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

[FEAT]: Header authentication to support various forms of auth and SSO #696

Closed
icsy7867 opened this issue Feb 8, 2024 · 1 comment
Closed
Labels
enhancement New feature or request feature request

Comments

@icsy7867
Copy link

icsy7867 commented Feb 8, 2024

What would you like to see?

Header auth using sso/saml is one of my favorite and easiest ways to implement SSO to a page.

Authelia is one popular tool, as well as apache Mellon. These tools basically set a header variable for a username after it has successfully authenticated the user.

Netbox Has an excellent implementation of this
https://demo.netbox.dev/static/docs/administration/authentication/

For authentication on the app side, if header auth is enabled, the built in login mechanism is disabled. The app generally reads the REMOTE_User header value. If it's set, register the user and authenticate them automatically.

Typically for sso/saml you can control who has access on the idp side. SSO services can even pass through groups or AD groups which gives some neat possibilities in an enterprise setting.

Awesome tool! I know your busy with it, but just wanted to toss this one out there.

@icsy7867 icsy7867 added enhancement New feature or request feature request labels Feb 8, 2024
@icsy7867 icsy7867 changed the title [FEAT]: Header authenticatio to support various forms of auth and SSO [FEAT]: Header authentication to support various forms of auth and SSO Feb 9, 2024
@timothycarambat
Copy link
Member

Moving convo to #1193

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

No branches or pull requests

2 participants