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

Allow only normalized URLs in requests caused a regression in view authz permission details in Admin Consol [GHI#44056]

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

      After allowing only normalized URLs in requests (#43765), users can't view/edit permissions in Client Authorization tab in the Admin Console. Once the user clicks on a Permission the UI crashes with this error missingNormalization.

      Version

      26.4.4

      Regression

      [x] The issue is a regression

      Expected behavior

      User should be able to view a client permission.

      Actual behavior

      UI crashes with error missingNormalization.

      How to Reproduce?

      1. In the Admin Console, create a new Client. Enable Authorization.
      2. Go to the Authorization tab. Then Permissions tab.
      3. Click on the Default Permission.
      4. The UI will crash.

      <img width="638" height="124" alt="Image" src="https://github.com/user-attachments/assets/b29aa869-2786-4ffc-b6b4-3f7e6818667e" />

      Anything else?

      • The issue doesn't happen if you set http-accept-non-normalized-paths to true.
      • The cause of the issue is that the UI code calls the REST API {{/auth/admin/realms/ {realmId}

        /clients/

        {clientId}

        /authz/resource-server/policy/

        {policyType}

        /

        {policyId}

        }} with empty policyType which results in double slashes in the URL.

      • After checking the code, in ResourcesPolicySelect.tsx calls findOnePolicy() with empty type here.

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

                Created:
                Updated:
                Resolved: