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

OpenID Connect #126

Open
rucciva opened this issue Apr 22, 2019 · 3 comments
Open

OpenID Connect #126

rucciva opened this issue Apr 22, 2019 · 3 comments

Comments

@rucciva
Copy link

rucciva commented Apr 22, 2019

Hi, is there any plan to include OpenID Connect as a backend?

Thanks

@smancke
Copy link
Member

smancke commented Apr 22, 2019

The OAuth Backends (e.g. the google one) are indeed doing OpenID Connect, if I got the Idea behind OpenID Connect right.

@rucciva
Copy link
Author

rucciva commented Apr 22, 2019

OpenID Connect is a standard so i think it should be possible to be used with another OpenID Connect provider besides google. Most of OpenID Connect relying party that i have encountered usually need to point to the /.well-known/openid-configuration URL or directly storing the configuration. Here are an example from sonarqube.

i think by implementing the openid connect, loginsrv (and i hope caddy too) will be able to integrate with multiple OAuth2 based identity provider. the client libraries are also available, e.g. https://github.com/coreos/go-oidc

@smancke
Copy link
Member

smancke commented Apr 22, 2019

OK, would be a good idea to make a generic backend which uses the discovery document and does the configuration dynamically.

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