We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Is your feature request related to a problem? Please describe. For some applications I want to login with URI only because they don't support custom headers. I thought it would be possible as I read the docs (https://docs.goauthentik.io/docs/add-secure-apps/providers/proxy/header_authentication#receiving-http-basic-authentication-authentik-20231), but somehow it doesn't work. If I sent the authentication header via Restman it works correctly so I don't think my traefik filters something. (other apps with http_basic auth work)
Describe the solution you'd like Support something like https://username:[email protected] (or maybe https://username:[email protected]) and for token https://domain.com/?ak_token=token (the original would be "?access_token=", but I think this would create some collisions with the applications behind authentik.
Additional context
#12489
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is your feature request related to a problem? Please describe.
For some applications I want to login with URI only because they don't support custom headers. I thought it would be possible as I read the docs (https://docs.goauthentik.io/docs/add-secure-apps/providers/proxy/header_authentication#receiving-http-basic-authentication-authentik-20231), but somehow it doesn't work. If I sent the authentication header via Restman it works correctly so I don't think my traefik filters something. (other apps with http_basic auth work)
Describe the solution you'd like
Support something like https://username:[email protected] (or maybe https://username:[email protected]) and for token https://domain.com/?ak_token=token (the original would be "?access_token=", but I think this would create some collisions with the applications behind authentik.
Additional context
#12489
The text was updated successfully, but these errors were encountered: