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

multiple ldap url's not working on one realm [GHI#31267]

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

      ldap

      Describe the bug

      I have a realm where I connect to one ldap instance. There, I configured to url's for redundancy.
      The thing is that whenever I test the connection, it gives me this error on gui:

      <img width="665" alt="Screenshot 2024-07-13 at 07 33 56" src="https://github.com/user-attachments/assets/58afa737-36af-496e-aeb4-3974e26ef9cd">

      Individually, both url's work fine.
      I see nothing at all on the logs.
      When I save it, I can still search users. But if the first url is down, it doesn't retrieve users using the second url

      In a brand new realm, I can do this normally, and I got no error whatsoever. So something might be broken underneath.

      Version

      25.0.1

      Regression

      [x] The issue is a regression

      Expected behavior

      Get a successful test connection when using multiple ldap url's.
      Getting redundancy by setting up two url's.

      Actual behavior

      I get an error when testing two otherwise working ldap urls when configuring ldap user storage to use them.
      I don't get the second url to work. When the first url is down, no search is made on the second.

      How to Reproduce?

      I don't know. I can't reproduce this on another realm.

      Anything else?

      No response

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

                Created:
                Updated:
                Resolved: