-
Notifications
You must be signed in to change notification settings - Fork 351
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
OAuthgrant filter does not work with GET /userinfo as the tokeninfo URL #3226
Comments
Hello. There is a Line 497 in bd87e31
Could you please try |
I also think this Line 166 in bd87e31
should be set only when TokeninfoSubjectKey is not empty Lines 158 to 164 in bd87e31
such that existing sub claim is not overwritten when -oauth2-tokeninfo-subject-key=''
|
Yes, this worked with the Okta GET /userinfo endpoint. |
Describe the bug
The OAuthgrant filter requires a tokeninfo URL which is only called by a GET request. However some IDPs like Okta have already deprecated this call. Specifically it looks for a uid field and it it fails, it will do a redirect. This leads to a redirect loop.
Using the GET /userinfo does not resolve this issue, as in Okta's case specifically the uid field does not exist in GET /userinfo. https://developer.okta.com/docs/api/openapi/okta-oauth/oauth/tag/OrgAS/#tag/OrgAS/operation/userinfo
To Reproduce
oauth.eskip file
dashboard: * -> oauthGrant() -> inlineContent("It works!") -> <shunt>;
Expected behavior
Observed behavior
Failed to create token container: tokeninfo subject key 'uid' is missing.
I think it should not rely on the uid field and work with GET /userinfo like the oidc filter.
The text was updated successfully, but these errors were encountered: