8000 Scope bug in device authorization request · Issue #9617 · keycloak/keycloak · GitHub
[go: up one dir, main page]

Skip to content

Scope bug in device authorization request #9617

Closed

Description

@cgeorgilakis

Describe the bug

According to the Device AuthZ Grant specification (see Section 3.1), the device authorization request supports requesting the scope of the access request through the scope (optional) parameter.

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.

Anything else?

No response

Activity

  1. added 2 commits that reference this issue on Jan 18, 2022
    f513b05
    b5e56ea
  2. added this to the 17.0.0 milestone on Jan 19, 2022
  3. added a commit that references this issue on Jan 19, 2022
    0c9ab32
  4. added a commit that references this issue on Jan 20, 2022
    eeb586c
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugCategorizes a PR related to a bug

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      0