[PR #744] [MERGED] Use correct Manager DN in Jenkins configuration #927

New issue

Closed

opened 2026-02-27 09:10:16 +03:00 by kerem · 0 comments

kerem commented

2026-02-27 09:10:16 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/lldap/lldap/pull/744
Author: @lvillis
Created: 11/23/2023
Status: ✅ Merged
Merged: 11/23/2023
Merged by: @nitnelave

Base: main ← Head: patch-1

📝 Commits (1)

13784dd chore(docs): update jenkins.md

📊 Changes

1 file changed (+1 additions, -1 deletions)

View changed files

📝 example_configs/jenkins.md (+1 -1)

📄 Description

Referring to the official documentation, the Manager DN should contain 'dc'

If your LDAP server doesn't support anonymous binding (IOW, if your LDAP server doesn't even allow a query without authentication), then Jenkins would have to first authenticate itself against the LDAP server, and Jenkins does that by sending "manager" DN and password.
A DN typically looks like CN=MyUser,CN=Users,DC=mydomain,DC=com although the exact sequence of tokens depends on the LDAP server configuration. It can be any valid DN as long as LDAP allows this user to query data.

This configuration is also useful when you are connecting to Active Directory from a Unix machine, as AD doesn't allow anonymous bind by default. But if you can't figure this out, you can also change AD setting to allow anonymous bind. See this document for how to.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/lldap/lldap/pull/744 **Author:** [@lvillis](https://github.com/lvillis) **Created:** 11/23/2023 **Status:** ✅ Merged **Merged:** 11/23/2023 **Merged by:** [@nitnelave](https://github.com/nitnelave) **Base:** `main` ← **Head:** `patch-1` --- ### 📝 Commits (1) - [`13784dd`](https://github.com/lldap/lldap/commit/13784dd177b0b210cac406da4e51fce75c64d56f) chore(docs): update jenkins.md ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `example_configs/jenkins.md` (+1 -1) </details> ### 📄 Description Referring to the official documentation, the Manager DN should contain 'dc' > If your LDAP server doesn't support [anonymous binding](http://www.google.com/?q=LDAP+anonymous+bind) (IOW, if your LDAP server doesn't even allow a query without authentication), then Jenkins would have to first authenticate itself against the LDAP server, and Jenkins does that by sending "manager" DN and password. A DN typically looks like CN=MyUser,CN=Users,DC=mydomain,DC=com although the exact sequence of tokens depends on the LDAP server configuration. It can be any valid DN as long as LDAP allows this user to query data. > This configuration is also useful when you are connecting to Active Directory from a Unix machine, as AD doesn't allow anonymous bind by default. But if you can't figure this out, you can also change AD setting to allow anonymous bind. See [this document](http://www.novell.com/coolsolutions/appnote/15120.html) for how to. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>