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

Change Client Templates to Client Scope

    XMLWordPrintable

Details

    • Feature Request
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Done
    • None
    • 4.0.0.Final
    • None
    • Keycloak Sprint 2, Keycloak Sprint 3, Keycloak Sprint 5, Keycloak Sprint 6, Keycloak Sprint 7
    • NEW
    • NEW

    Description

      This JIRA has a dependency on adding OAuth scope support as well.

      Was thinking that we should rename Client Templates to Client Scopes.
      For oauth, oidc, and token exchange client asks for a specific scope
      with the "scope" parameter. This "scope" parameter would be the name
      of a client-id or a client scope (formerly client emplates. Clients
      will be granted access to scopes in the admin console.

      Our consent screen logic is a mess. We loop through every protocol
      mapper and role stuffed in the token to blurt out a message on the
      consent screen for each. Its messy, ugly, and not very easy to make
      it look like you want. If we have Client Scopes, then clients can
      consolidate mappers and roles into a single consent message that covers that group of mappers and role scopes.

      Attachments

        Issue Links

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: