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

[jenkins-infra-bot]

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

[jenkins-infra-bot]

pedersen:

• Original comment link
• Raw content of original comment:

  You do not mention which versions you upgraded from. I suspect it could be [JENKINS-70492] Only trigger SecurityListener on real authentication username/password #162 that causes this behaviour ( the NamingException never gets thrown). The only other change I see would be the switch to SpringSecurity.
  

You do not mention which versions you upgraded from. I suspect it could be #162 that causes this behaviour ( the NamingException never gets thrown). The only other change I see would be the switch to SpringSecurity.

[jenkins-infra-bot]

efetzer:

• Original comment link
• Raw content of original comment:

  I upgraded from 2.504.3.  The upgrade forced me to upgrade the AD plugin.  Once upgraded I can no longer have a local user function along side of AD being activated.
  

I upgraded from 2.504.3.  The upgrade forced me to upgrade the AD plugin.  Once upgraded I can no longer have a local user function along side of AD being activated.