Uploaded image for project: 'Keycloak'
  1. Keycloak
  2. KEYCLOAK-18418 User Profile [supported]
  3. KEYCLOAK-18433

Allow mapping user attributes when federating users through brokering

    XMLWordPrintable

Details

    • Sub-task
    • Resolution: Unresolved
    • Major
    • None
    • None
    • Core
    • None
    • Keycloak Sprint 56
    • NEW
    • NEW

    Description

      In order to provide a better experience when mapping user attributes from identity providers, Keycloak should allow mapping the attributes based on the user profile configuration.

      This mapper should be able to:

      • List the available attributes from the user profile configuration and respecting their permissions
      • Suggest as the Claim the name of the attribute with the option to change it.

      Today, we have the `Attribute Importer` mapper that forces administrators to type the name of the user attribute. Perhaps, we can introduce a new property to select attributes from the user profile configuration.

      Attachments

        Activity

          Public project attachment banner

            context keys: [headless, issue, helper, isAsynchronousRequest, project, action, user]
            current Project key: KEYCLOAK

            People

              psilva@redhat.com Pedro Igor Craveiro
              psilva@redhat.com Pedro Igor Craveiro
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: