[JENKINS-76132] AD Plugin No Longer Allows Fallback to Jenkins Internal User Database

After upgrading to the Jenkins 2.516.1 and AD 2.40, I can no longer get Jenkins Internal Users to authenticate via the command line.  They can't login to the portal either.  Before this upgrade I was able to authenticate using the CLI from an external server with a command such as:

ssh -p myPort myJenkinsInternalUser@​myJenkinsMachine whoami

 

This no longer works, and thus, my application which I designed to start all of my Jenkins builds and deploys no longer functions unless I shut down Jenkins security.

---
Originally reported by efetzer, imported from: AD Plugin No Longer Allows Fallback to Jenkins Internal User Database

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

Raw content of original issue

After upgrading to the Jenkins 2.516.1 and AD 2.40, I can no longer get Jenkins Internal Users to authenticate via the command line.  They can't login to the portal either.  Before this upgrade I was able to authenticate using the CLI from an external server with a command such as:


ssh -p myPort myJenkinsInternalUser@myJenkinsMachine whoami


 


This no longer works, and thus, my application which I designed to start all of my Jenkins builds and deploys no longer functions unless I shut down Jenkins security.

• environment: Jenkins 2.516.1, AD Plugin 2.40

Reproduce the failure with Jenkins 2.516.1 and Active Directory plugin 2.40 using the reported SSH CLI command, then check whether Jenkins Internal Users can authenticate through the portal. The work is complete when internal users can authenticate through both paths while Active Directory security remains enabled.

Written by the indexing model from the issue text.