Skip to content

Authorization Server consent fails on client with no registered scopes #18565

@Kehrlann

Description

@Kehrlann

Describe the bug

If a registered client supporting the authorization_code has no scopes, and requires authorization consent.
When a client makes an authorization request decision, they see a consent screen with no scopes displayed (see screenshot).
If the user clicks "submit consent", an oauth2 error redirect happens, because it is expected that there is at least one scope consented to (source)

Expected behavior

I see three options:

  • Disallow the "require consent + 0 scope" combination for clients
  • Allow the combination but skip the consent screen
  • Allow the combination, present the screen and allow the user to click "submit consent"

Screenshot

Image

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions