Testing ldap connection should not process or bind the credentials

[pedroigor]

Closes #30821
Closes #31001

[rmartinc]

Thanks @pedroigor! LGTM!

[stianst]

Approving based on previous reviews

[puggimer]

I tested this by running from quay.io/keycloak/keycloak:nightly today (July 9th, 2024). It still failed.
To make a better test case (I hope), I created a new realm. Then I added an Active Directory ldap. I tested connection, it passed. I tested authentication, it passed (though the message it gave was "Successfully connected to LDAP". Then I saved it. Clicked test connection and it now fails. Clicked test authentication it now fails. Reset the BindCredentials to the original value and both test succeed until I save it, then they fail again. (see #31001 ).

This now seems to be happening consistently - I cannot save and use an AD federation on the nightly build because the bindCredentials is always reset (since it is masked I don't know what it is set to).

I am attaching the new realm, and the trace log (though there is nothing in the log when the errors occur)

One note - this only happens when using ACTIVE DIRECTORY as the vendor. Using OTHER it works as expected. (I don't have Red Hat, Tivoli or Novell to test against)

realm-export.zip
keycloak.zip

[rmartinc]

Argggh! It's because you are using email format for the bind DN and not a proper DN. If you use a Dn instead of the email of the admin proxy user in ldap it will work. I'm going to file a new issue. It's incredible the mess I did with such a simple change. Sorry.

[puggimer]

Hmmm - when I was given the credentials is was the email address and password which worked before.
Took me a while to find the DN for the account, but using that the issue goes away (well the mask still changes size, which is a bit weird to me, but inconsequential.
Thanks!!!

[rmartinc]

I created #31196 for the samaccountname@domain format.

[puggimer]

Thanks - but I think you meant to reference #31196