Uploaded image for project: 'Keycloak'
  1. Keycloak
  2. KEYCLOAK-349

Scope query parameter support

    XMLWordPrintable

Details

    • Feature Request
    • Status: Closed
    • Major
    • Resolution: Done
    • None
    • 4.0.0.Final
    • OIDC
    • Keycloak Sprint 2, Keycloak Sprint 3, Keycloak Sprint 5, Keycloak Sprint 6, Keycloak Sprint 7

    Description

      There's currently very limited support for scope query parameter. This is limited to a few hard coded scopes (i.e. offline_access) and the ability to map a single role to a scope. We should add the option to define custom scopes which can decide what protocol mappers and roles are included in the token. There should also be built-in support for default scopes defined by OpenID Connect.

      Attachments

        1. scope-address_WARNING.txt
          15 kB
        2. scope-all_WARNING.txt
          15 kB
        3. scope-claims_WARNING.txt
          15 kB
        4. scope-email_WARNING.txt
          15 kB
        5. scope-phone_WARNING.txt
          15 kB

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. KEYCLOAK-3467 Support for OAuth scope attribute

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is duplicated by

          Feature Request - Feature requests from customers and/or users KEYCLOAK-348 Support scope query parameter

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. KEYCLOAK-3467 Support for OAuth scope attribute

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is incorporated by

          Task - A task that needs to be done. KEYCLOAK-6630 Rename client templates to client scopes

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Sub-task - The sub-task of the issue KEYCLOAK-3177 Pass OIDC Basic Profile

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Feature Request - Feature requests from customers and/or users KEYCLOAK-5579 Change Client Templates to Client Scope

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Feature Request - Feature requests from customers and/or users KEYCLOAK-5613 Add support for MP-JWT tokens client scope

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. KEYCLOAK-6170 Multiple offline sessions issued from the same user session fails token refresh

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              mposolda@redhat.com Marek Posolda
              patriot1burke@gmail.com Bill Burke (Inactive)
              Votes:
              12 Vote for this issue
              Watchers:
              19 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: