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

Service accounts visible under user search in Admin console [GHI#34233]

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

      In Keycloak version 26.0.1, the introduction of the exact parameter in the /admin/realms/master/ui-ext/brute-force-user endpoint has resulted in unintended filtering behavior for service accounts. When the exact parameter is not specified, it defaults to false, which inadvertently affects the search results for users, particularly service accounts.

      Version

      26.0.1

      Regression

      [X] The issue is a regression

      Expected behavior

      Service accounts should not be visible under user search in Admin console.

      Actual behavior

      Service accounts visible under user search in Admin console.

      How to Reproduce?

      Just create client with service accounts enabled and see the users!.

      Anything else?

      Below is the change in admin ui that caused the issue .

      <img width="698" alt="image" src="https://github.com/user-attachments/assets/468bd8ce-209a-4275-ae13-318516fc0384">

      I feel instead of making change in frontend , we can improve backend see the below snip.
      /admin-ui-ext/src/main/java/org/keycloak/admin/ui/rest/BruteForceUsersResource.java

      <img width="628" alt="image" src="https://github.com/user-attachments/assets/cd67ffd6-300e-476b-9963-5e0c735d8b3d">

      Because of exact flag in request the else if(Line:133) part is getting executed and the we are setting service-account flag by default to true!

      Can we change that to false ?

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

                Created:
                Updated:
                Resolved: