-
Notifications
You must be signed in to change notification settings - Fork 437
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
Allowing Custom SSO Auth Header #468
Comments
Thank you for your feedback. In fact, using the following configuration should work properly.
Different from the examples in Authelia's documentation, https://www.authelia.com/integration/proxies/nginx/#authelia-authrequestconf |
This would be an elegant solution for Nginx reverse proxy user, thanks for sharing! My use case is a bit different, I'm using Kubernetes + nginx ingress controller, which has a more convoluted syntax and less documentation on this topic. In case it helps someone, here's how to configure nginx ingress annotations to pass X-Email in addition to Remote-Email:
@BobDu would you consider accepting a PR to make the auth header configurable, I feel that this could be beneficial for people with different proxy setups. |
Amazing project! I'm very thrilled to be trying out the new SSO Auth Header feature.
I noticed a small hiccup when integrating with Athelia:
Athelia uses the
Remote-User
andRemote-Email
instead ofX-Email
as auth header returned to reverse proxy: https://www.authelia.com/integration/trusted-header-sso/introduction/#response-headersThis means that the SSO won't work out of the box with Authelia.
Adding a new env parameter for header name would provide this flexibility.
The text was updated successfully, but these errors were encountered: