Uploaded image for project: 'Red Hat build of Keycloak'
  1. Red Hat build of Keycloak
  2. RHBK-2459

[Admin UI] [Create resource-based permission] Resource input is disabled [GHI#34678]

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False

      Before reporting an issue

      [X] I have read and understood the above terms for submitting issues, and I understand that my issue may be closed without action if I do not follow them.

      Area

      admin/ui

      Describe the bug

      Background

      The clients with the enabled fine-grained authorization have the Authority tab, where the resources and the accompanying policies and permissions can be defined.

      The admin can create a resource-based permission for the given resource in the table simply by clicking the "Create permission" next to the resource of interest.

      !377258023-2c99fa4a-2182-499d-b483-56657a8fb641

      After clicking on the Create permission button, the user is redirected to the Create resource-based permission form with the pre-filled data, based on the selected resource.

      e.g.

      !377258325-b2dfccb3-0d46-47c8-8d7b-2fdfcc6ee873

      Problem

      The Resource input is disabled. It's not possible to choose a different resource or add an another one.

      However, when the permission is being created via the Authorization -> Permissions -> Create permission -> Create resource-based permission, the Resource input is editable and selecting multiple resources is possible.

      !image

      !image

      Version

      26.0.5

      Regression

      [X] The issue is a regression

      Expected behavior

      The Resource input is not disabled in any of the described scenarios. The admin user can change resource, add more resources via the dropdown input freely.

      Actual behavior

      The Resource input is disabled. The admin user can't change resource, nor can't the admin add more resource(s).

      How to Reproduce?

      1. Start up Keycloak
      2. Navigate to Clients, select Import client
      3. Upload the demo client with the Authorization enabled, e.g. : https://gist.github.com/rh-/e0ddf9d94f48efc2812c5c7612036264
      4. Navigate to the newly imported client demo-resource-permission-selection -> Authorization -> Resources
      5. Click Create permission next to a resource

      Anything else?

      This worked as expected in 25.0.6.
      The problem first appeared in 26.0.0 and it remains through the 26.0.5.

              Unassigned Unassigned
              pvlha Pavel Vlha
              Keycloak UI
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: