Skip to content
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

OIDC: Use 'userinfo' endpoint when userinfo data are not sent along with ID token. #964

Closed
1 of 4 tasks
psrok1 opened this issue Aug 6, 2024 · 0 comments · Fixed by #972
Closed
1 of 4 tasks

OIDC: Use 'userinfo' endpoint when userinfo data are not sent along with ID token. #964

psrok1 opened this issue Aug 6, 2024 · 0 comments · Fixed by #972
Labels
type:improvement Small improvement of existing feature zone:backend MWDB backend core related tasks

Comments

@psrok1
Copy link
Member

psrok1 commented Aug 6, 2024

Feature Category

  • Correctness
  • User Interface / User Experience
  • Performance
  • Other (please explain)

Describe the problem

In current implementation we don't use /userinfo endpoint at all because Keycloak sends user information along with ID token. Unfortunately it's not that common as we thought.

Describe the solution you'd like

If there are no extra information about the user: e-mail, username (["preferred_username", "nickname", "name"]) in the /token response, ask /userinfo.

@psrok1 psrok1 added zone:backend MWDB backend core related tasks type:improvement Small improvement of existing feature labels Aug 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:improvement Small improvement of existing feature zone:backend MWDB backend core related tasks
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant