Details
-
Bug
-
Status: Resolved (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
Description
When testing the AD connection details you need to actually do a search to make sure the credential is valid.
If in this search there are not elements, we are returning null.
And in this case we are saying that everything is success.
it might happen that under AD replication farm one of the AD instances is broken not returning any user in the search. In this case, we should expose the issue on the GUI.
Code changed in jenkins
User: Felix Belzunce Arcos
Path:
src/main/java/hudson/plugins/active_directory/ActiveDirectorySecurityRealm.java
src/main/resources/hudson/plugins/active_directory/Messages.properties
http://jenkins-ci.org/commit/active-directory-plugin/8a86022e18cb81dd4bc0e7ae9afd5a8cf048d894
Log:
Merge pull request #29 from fbelzunc/
JENKINS-34143[FIXED JENKINS-34143] Test Active Directory connection button reports success if the search operation doesn't have any result
Compare: https://github.com/jenkinsci/active-directory-plugin/compare/313942cef58e...8a86022e18cb