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
Is your feature request related to a problem? Please describe.
It can be confusing for a management user to see his/her name changed in the management UI since the first time s/he logged in. This situation may occur if an OAuth 2 token changes the user's identity after the initial token is refreshed.
The Identity Provider is who decides what information is carried in a token and whether the user's identity may change after the token has refreshed. However, as stated earlier, it can be confusing for end-users and therefore, it sounds reasonable to ensure that the identity does not change in the refreshed tokens.
Describe the solution you'd like
The solution is to ensure that the OAuth 2 plugin validates that the user's identity remain intact prior to replacing the current token for a new one.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
It can be confusing for a management user to see his/her name changed in the management UI since the first time s/he logged in. This situation may occur if an OAuth 2 token changes the user's identity after the initial token is refreshed.
The Identity Provider is who decides what information is carried in a token and whether the user's identity may change after the token has refreshed. However, as stated earlier, it can be confusing for end-users and therefore, it sounds reasonable to ensure that the identity does not change in the refreshed tokens.
Describe the solution you'd like
The solution is to ensure that the OAuth 2 plugin validates that the user's identity remain intact prior to replacing the current token for a new one.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: