You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The UserInfo type definition should include all the properties that are liable to appear. I think it's only missing preferred_username atm, but it let's make sure.
Any changes need to be defined in each package in order to make types declarations available to the end user.
More Context
The userInfo property is the payload from GET /oauth2/userinfo. This type of userinfo response is an OIDC standard. (Docs for this endpoint)
See the changes to 1.50 too. From the release notes:
Applications now have a new Scope Handling Policy. The Strict option provides behaviors that are more compliant with the OIDC specification, while the Compatibility option provides backwards-compatible behavior. Specifically, Strict mode limits information in access tokens and populates Id tokens and UserInfo responses based on the requested OAuth scopes. This option also restricts the UserInfo endpoint to accepting only access tokens containing the openid scope.
Audit
UserInfo
type def.Description
The
UserInfo
type definition should include all the properties that are liable to appear. I think it's only missingpreferred_username
atm, but it let's make sure.Any changes need to be defined in each package in order to make types declarations available to the end user.
More Context
The
userInfo
property is the payload fromGET /oauth2/userinfo
. This type of userinfo response is an OIDC standard. (Docs for this endpoint)This ticket was tipped off from #94
The text was updated successfully, but these errors were encountered: