jenkinsci / jenkinsci/active-directory-plugin

[JENKINS-72472] Anonymous auth not configurable using jenkins.yaml

Open
#656 1 comment 0 reactions 0 assignees View on GitHub
component:active-directory-plugin imported-jira-issue priority:minor resolution:unresolved
Dominant language
Java
Stars
53
Forks
115
PR merge metrics
No merged PRs in 30d

Description

The Active Directory Plugin cant be configured to use anynomymous auth to the ldap server using the jenkins.yaml through the infrasstructure as acode plugin.

If I configure it in the UI (which works only up to the next restart), the generated jenkins.yaml will look like something like this:

 

securityRealm:

    activeDirectory:

      bindPassword: "{AQAAABAAAAAQT1Y8TFig7L+fUeh1qa=}"

      customDomain: true

      domains:

      - bindPassword: "{AQAAABAAAAAQcFI66yMD9kUdg6nmR=}"

        name: "ham.example.de"

        servers: "server1.ham.example.de"

        site: "ham.example.de"

        tlsConfiguration: TRUST_ALL_CERTIFICATES

      groupLookupStrategy: TOKENGROUPS

      removeIrrelevantGroups: false

      requireTLS: true

      startTls: true

  

Note I didnt enter any username/Password in the UI. 

Once I remove these bindPassword lines and do a redeploy the configuration will be omitted and Jenkins will fallback to the internal user database.

This looks like a bug.

---
Originally reported by yves_harms_ituv, imported from: Anonymous auth not configurable using jenkins.yaml


  • 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 Active Directory Plugin cant be configured to use anynomymous auth to the ldap server using the jenkins.yaml through the infrasstructure as acode plugin.
If I configure it in the UI (which works only up to the next restart), the generated jenkins.yaml will look like something like this:
 
securityRealm:
    activeDirectory:
      bindPassword: "{AQAAABAAAAAQT1Y8TFig7L+fUeh1qa=}"
      customDomain: true
      domains:
      - bindPassword: "{AQAAABAAAAAQcFI66yMD9kUdg6nmR=}"
        name: "ham.example.de"
        servers: "server1.ham.example.de"
        site: "ham.example.de"
        tlsConfiguration: TRUST_ALL_CERTIFICATES
      groupLookupStrategy: TOKENGROUPS
      removeIrrelevantGroups: false
      requireTLS: true
      startTls: true
  
Note I didnt enter any username/Password in the UI. 
Once I remove these bindPassword lines and do a redeploy the configuration will be omitted and Jenkins will fallback to the internal user database.
This looks like a bug.

environment

```
Active Directory plugin Version2.34

Jenkins 2.426.1
```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.