[JENKINS-73264] Issue with adding AD information

When adding domain information in Jenkins Security (such as Domain Name, Domain controller, Bind DN, Bind Password) and clicking Test Domain in works correctly.

 

After clicking apply, in Domain controller section there is automatically added port 3268 and Active Directory Authentication stops working (Can't authenticate using AD user).

Workaround for it is to remove port from Jenkins config.xml file and restart Jenkins server. After restarting AD Authentication works.

---
Originally reported by lmedoshvili, imported from: Issue with adding AD information

• assignee: fbelzunc
  
• status: Open
  
• priority: Minor
  
• component(s): active-directory-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 1
  
• imported: 2025-12-07
  

Raw content of original issue

When adding domain information in Jenkins Security (such as Domain Name, Domain controller, Bind DN, Bind Password) and clicking Test Domain in works correctly.


 


After clicking apply, in Domain controller section there is automatically added port 3268 and Active Directory Authentication stops working (Can't authenticate using AD user).


Workaround for it is to remove port from Jenkins config.xml file and restart Jenkins server. After restarting AD Authentication works.

environment

```
OS: Rocky Linux 9.4

Jenkins 2.452.1

Active Directory plugin 2.35

```

Start by reproducing the issue in Jenkins Security using the reported Jenkins and Active Directory plugin versions. Compare the Test Domain and Apply flows, then inspect config.xml to determine why port 3268 is added to the Domain controller. Done means applying the configuration does not break Active Directory authentication and the workaround is no longer needed.

Written by the indexing model from the issue text.