-
Notifications
You must be signed in to change notification settings - Fork 401
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
No way to check if server supports UserInfo #373
Comments
Does something like the following work? (sorry, Claims is probably a bad name for "inspect the provider config") https://pkg.go.dev/github.com/coreos/go-oidc/v3/oidc#Provider.Claims
|
raggi
added a commit
to raggi/go-oidc
that referenced
this issue
Apr 24, 2023
This enables users detect if the provider.UserInfo method would fail ahead of time, by checking for the empty string in UserInfoEndpoint. Fixes coreos#373 Fixes coreos#374
lukaszraczylo
pushed a commit
to lukaszraczylo/go-oidc
that referenced
this issue
Apr 13, 2024
This enables users detect if the provider.UserInfo method would fail ahead of time, by checking for the empty string in UserInfoEndpoint. Fixes coreos#373 Fixes coreos#374
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The server's
.well-known/openid-configuration
reports a UserInfo endpoint which is used in theUserInfo
method. If the OIDC provider does not report an endpoint, UserInfo reports an error. But there is no way programmatically check beforehand and no way to check the error message other than string matching:It would be nice if it were possible to avoid string matching on the error. Perhaps either something to pass to
errors.Is
or a mechanism for inspecting the contents of the.well-known/openid-configuration
that the package fetched?The text was updated successfully, but these errors were encountered: