Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Broken OIDC integration with Dex #4001

Open
jfstenuit opened this issue Jan 8, 2025 · 1 comment
Open

Broken OIDC integration with Dex #4001

jfstenuit opened this issue Jan 8, 2025 · 1 comment

Comments

@jfstenuit
Copy link

In my set-up, I have Velociraptor served under /vraptor and Dex served under /auth. NginX takes care of serving the requests to the correct back-end. (Dex is an OIDC IdP written in Go).

Velociraptor configuration is as follow :

GUI:
  bind_address: 127.0.0.1
  bind_port: 8889
  use_plain_http: true
  base_path: /vraptor
  gw_certificate: |
redacted
  gw_private_key: |
redacted
  public_url: https://host.domain.tld/vraptor
  links:
  - text: Documentation
    url: https://docs.velociraptor.app/
    icon_url:
redacted
    type: sidebar
    new_tab: true
  authenticator:
    type: oidc
    oidc_issuer: https://host.domain.tld/auth
    oauth_client_id: velociraptor-client
    oauth_client_secret: redacted

The IDP respond properly at https://host.domain.tld/auth/.well-known/openid-configuration

But velociraptor never tries to reach the OIDC authorization_endpoint URL. When clicking on "Sign in with Generic OIDC Connector" on page https://host.domain.tld/vraptor/app/index.html , the url requested is https://host.domain.tld/vraptor/vraptor/auth/oidc/login which directly 302-redirects to /vraptor/app/index.html .

There is no indication of an error in the OIDC configuration, neither trough the GUI nor through the logs.

If there is something broken with the OIDC IdP (either because of the configuration of Velociraptor or because of the features supported by the IdP), there should at least be an indicative message in the logs.

@scudette
Copy link
Contributor

Can you please test this configuration with the latest ci build? There have been some changes related to base path handling which might be broken in 0.73.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants