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
Hi, guys!
What do you think about supporting device flow authorization?
Configuration .well-known/openid-configuration contains device_authorization_endpoint like {{KEYCLOAK_URL}}/realms/{{KEYCLOAK_REALM}}/protocol/openid-connect/auth/device
.well-known/openid-configuration
device_authorization_endpoint
I think adding URL into providerJSON/Provider and a method like here for waiting for token
providerJSON/Provider
The text was updated successfully, but these errors were encountered:
Hey!
The spec you're referring to (https://www.rfc-editor.org/rfc/rfc8628.html) is an OAuth 2.0 specification. It's not related to OpenID Connect (https://openid.net/developers/specs/).
This issue is likely better for Go's oauth2 repo: https://github.com/golang/oauth2
Going to close out since go-oidc is focused on OpenID Connect, not OAuth 2.0. But please re-open if I've misunderstood.
Sorry, something went wrong.
Ok, thanks! Issue here
No branches or pull requests
Hi, guys!
What do you think about supporting device flow authorization?
Configuration
.well-known/openid-configuration
containsdevice_authorization_endpoint
like {{KEYCLOAK_URL}}/realms/{{KEYCLOAK_REALM}}/protocol/openid-connect/auth/device
I think adding URL into
providerJSON/Provider
and a method like here for waiting for tokenThe text was updated successfully, but these errors were encountered: