[JENKINS-67865] AD Plugin 2.25.1 - Use Jenkins Internal Database Broken

The Jenkins Internal DB fallback user is not longer functioning. Per logs, the plugin treats it as a regular bound AD user even when no AD server is bound.

---
Originally reported by nbgibson, imported from: AD Plugin 2.25.1 - Use Jenkins Internal Database Broken

• 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

The Jenkins Internal DB fallback user is not longer functioning. Per logs, the plugin treats it as a regular bound AD user even when no AD server is bound.

• environment: RHEL 8, Jenkins 2.335, AD Plugin 2.25.1

Start by reproducing the Jenkins Internal DB fallback-user failure in the stated RHEL 8, Jenkins 2.335, and AD Plugin 2.25.1 environment, then inspect the active-directory-plugin authentication path and logs when no AD server is bound. Done means the Jenkins Internal DB fallback user works without an AD server while bound AD users continue to behave correctly.

Written by the indexing model from the issue text.