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

Support a dynamic update profile form

    XMLWordPrintable

Details

    • Sub-task
    • Resolution: Done
    • Major
    • None
    • None
    • Core

    Description

      Currently, the update profile form does not support the user profile configuration. In order to make it more dynamic, we should enhance it to dynamically render attributes as per user profile configuration.

      The work here should be similar to what was done to the `VerifyProfile` required action and its corresponding template, where attribute metadata is exposed including annotations.

      We could potentially remove the `VerifyProfile` required action if we think that we should always enforce profile updates whenever it is not compliant with the user profile configuration.

      Attachments

        Issue Links

          is blocked by

          Sub-task - The sub-task of the issue KEYCLOAK-18423 Support a user-friendly name property to attributes

          • 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.
          • Resolved
          is cloned by

          Sub-task - The sub-task of the issue KEYCLOAK-18591 Support a dynamic IDP user review form

          • 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

          Enhancement - An enhancement or refactoring of existing functionality KEYCLOAK-18541 Cleanup ftl templates for all dynamic user profile related actions (register, update/verify profile, IDP review)

          • 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.
          • Resolved

          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:
                1 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: