-
Notifications
You must be signed in to change notification settings - Fork 4
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
Oidc #1
Comments
I'm familiar with OIDC, especially since I use one (Keycloak) in my company, but I'm a bit rusty. It seems that zitadel is something similar. As I understand it, OIDC is an identity provider with OAuth2 capability. I can use the OAuth2 flow easily by parsing the discovery document (google example), and instead of calling the Github API to verify and retrieve user information, I can use the ID token, validate it by verifying a signature and certificates and retrieve user information using the OIDC-compliant While it seems interesting to extend the experiment to OIDC, it's a shame that Github doesn't support OIDC. I may extend the example with Google Auth, through. Theorically, it looks like I must:
To be fair, I should use the go-oidc package instead. And I should have used the package oauth2. Right now, the implementation is very "naive". |
Support added with |
zitadel/zitadel-go#236
I suggested your repo as a basis / example.
Maybe you also interested in a generic oidc / oath system based on htmx.
Zitadel also supports passkeys and other fancy stuff
The text was updated successfully, but these errors were encountered: