[JENKINS-66847] AD plugin doesn't use Jenkins credentials for bind dn and password

As the summary says, the AD plugin still uses custom fields for providing the bind dn and password instead of a credentials selector. This also makes it necessary to put a variable into JCasC files instead of a credentials ID which undermines security (because that variable has to be set somewhere).

Please fix.

---
Originally reported by dhs, imported from: AD plugin doesn't use Jenkins credentials for bind dn and password

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

Raw content of original issue

As the summary says, the AD plugin still uses custom fields for providing the bind dn and password instead of a credentials selector. This also makes it necessary to put a variable into JCasC files instead of a credentials ID which undermines security (because that variable has to be set somewhere).


Please fix.

• environment: Any

No source file or test is named. Start by locating the Active Directory plugin configuration entry point for the bind DN and password, then trace how Jenkins credentials and JCasC values are handled; done means the configuration uses a credentials selector and supports a credentials ID in JCasC instead of requiring a variable.

Written by the indexing model from the issue text.