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
However, Keycloak does not honour well the scope parameter (optional client scopes). This affects:
the consent which (when enabled) does not show the scopes requested in the device authorisation request
the UserInfo endpoint after a successful Device Access Token Request does not contains the claims mapped to the requested scopes
when the consent is enabled, the Device Access Token Request fails with the following message: { "error": "invalid_scope", "error_description": "Client no longer has requested consent from user"}
In order to solve this bug, requested scopes are added to 'scope' client note in authenticationSession after successfully verification.
Version
16.1.0
Expected behavior
No response
Actual behavior
No response
How to Reproduce?
Execute Device Authorization Request with scope parameter containing optional scopes of client.
For optional scope with consent 'Display On Consent Screen' equal to true bullet one and three will happen.
For optional scope with consent 'Display On Consent Screen' equal to false bullet two will happen.
Activity
Fix scope bug in device authorization request
Fix scope bug in device authorization request
Fix scope bug in device authorization request
Fix scope bug in device authorization request, Closes keycloak#9617