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

Account information should be dynamic based on the user profile configuration - backend part

    XMLWordPrintable

Details

    Description

      The account console should render user attributes dynamically based on the user profile configuration.

      It should be possible to pass over attribute metadata to the account console through the REST API by either creating a specific endpoint or decorating the user representation with the attribute metadata.

      Attachments

        Issue Links

          blocks

          Sub-task - The sub-task of the issue KEYCLOAK-18430 Account information should be dynamic based on the user profile configuration

          • 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.
          • Pull Request Sent
          duplicates

          Sub-task - The sub-task of the issue KEYCLOAK-18430 Account information should be dynamic based on the user profile configuration

          • 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.
          • Pull Request Sent
          is related to

          Bug - A problem which impairs or prevents the functions of the product. KEYCLOAK-19089 Account information should be dynamic based on the user profile configuration - Documentation of Keycloak Admin REST API

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Plan

          Activity

            Public project attachment banner

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

              People

                velias@redhat.com Vlastimil Eliáš
                psilva@redhat.com Pedro Igor Craveiro
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: