Add option in oidc to hit the optional userinfo endpoint#1433
Conversation
|
cc @ericchiang (as you seem to be the one working with PRs :) ) |
|
Why is okta not returning username, email or email verified in their id token? |
|
I'm not sure I follow the question? This PR (and the linked docs) talk about some claims missing due to "think tokens". I have provided both a link to their documentation which explains it and code which supports this functionality. As to why this provider decided to do thin tokens I cannot say, but from what I understand this is allowed by spec -- so it seems reasonable to me that dex should optionally support it. |
ericchiang
left a comment
There was a problem hiding this comment.
Couple comments. Please squash your commits when updating
Some oauth providers return "thin tokens" which won't include all of the claims requested. This simply adds an option which will make the oidc connector use the userinfo endpoint to fetch all the claims.
|
@ericchiang Updated to address comments. |
Add option in oidc to hit the optional userinfo endpoint
Some oauth providers return "thin tokens" which won't include all of the
claims requested. This simply adds an option which will make the oidc
connector use the userinfo endpoint to fetch all the claims.
as an example of an IDP that does this: https://support.okta.com/help/s/article/Okta-Groups-or-Attribute-Missing-from-Id-Token