[JENKINS-28233] Missing help files in LDAP configuration

[jenkins-infra-bot]

For Jenkins 1.577, several help files were moved to LDAP plugin and therefore deleted in core, see e91782e.
The LDAP plugin's version (1.6) was not updated to the version containing the help files (1.11), so the help links are invalid unless you manually update LDAP plugin to 1.11.

Example link:
Manage Jenkins/Configure Global Security/Access Control: Security Realm = LDAP, help for "Server"

---

Originally reported by albers, imported from: Missing help files in LDAP configuration

• assignee: albers
• status: Resolved
• priority: Trivial
• component(s): core, ldap-plugin
• label(s): 1.609.2-fixed
• resolution: Fixed
• resolved: 2015-06-08T16:39:58+00:00
• votes: 0
• watchers: 1
• imported: 2025-11-24

Raw content of original issue

For Jenkins 1.577, several help files were moved to LDAP plugin and therefore deleted in core, see e91782e.
The LDAP plugin's version (1.6) was not updated to the version containing the help files (1.11), so the help links are invalid unless you manually update LDAP plugin to 1.11.

Example link: 
Manage Jenkins/Configure Global Security/Access Control: Security Realm = LDAP, help for "Server"

[jenkins-infra-bot]

albers:

• Original comment link
• Raw content of original comment:

  resolved by Update bundled LDAP plugin in order to restore missing help files #1682
  

resolved by #1682

[jenkins-infra-bot]

albers:

• Original comment link
• Raw content of original comment:

  verified.
  

verified.

[jenkins-infra-bot]

danielbeck:

• Original comment link
• Raw content of original comment:

  https://github.com/jenkinsci/ldap-plugin/blob/master/pom.xml#L121 seems to me that this should be carefully considered.
  

https://github.com/jenkinsci/ldap-plugin/blob/master/pom.xml#L121 seems to me that this should be carefully considered.

[jenkins-infra-bot]

olivergondza:

• Original comment link
• Raw content of original comment:

  I agree the incomplete changelog does not fill me with confidence either. I presume reverting e91782e in stable branch would be less risky.
  

I agree the incomplete changelog does not fill me with confidence either. I presume reverting e91782e in stable branch would be less risky.

[jenkins-infra-bot]

danielbeck:

• Original comment link
• Raw content of original comment:

  Alternatively, create LDAP 1.6.1 for bundling with 1.609.x. Seems cleaner and we don't have to think about which files will get used with newer LDAP Plugin versions that also bundle them.
  

Alternatively, create LDAP 1.6.1 for bundling with 1.609.x. Seems cleaner and we don't have to think about which files will get used with newer LDAP Plugin versions that also bundle them.

[jenkins-infra-bot]

albers:

• Original comment link
• Raw content of original comment:

  Should I revert 824662a for now so that the plugin update does not make it into an official Jenkins version?
  

Should I revert 824662a for now so that the plugin update does not make it into an official Jenkins version?

[jenkins-infra-bot]

danielbeck:

• Original comment link
• Raw content of original comment:

  I'd like to know what's incompatible. The changelog seems to indicate this is only a warning about downgrading being broken, which we probably could ignore.
  

I'd like to know what's incompatible. The changelog seems to indicate this is only a warning about downgrading being broken, which we probably could ignore.

[jenkins-infra-bot]

danielbeck:

• Original comment link
• Raw content of original comment:

  jenkinsci/ldap-plugin@4a80681 seems harmless enough, so this seems fine despite the warning (in fact, it's a weird one as it only affects downgrading).
  

jenkinsci/ldap-plugin@4a80681 seems harmless enough, so this seems fine despite the warning (in fact, it's a weird one as it only affects downgrading).

[jenkins-infra-bot]

olivergondza:

• Original comment link
• Raw content of original comment:

  There is no reason to revert this on master. As it was not released yet I target this for 1.609.2.
  

There is no reason to revert this on master. As it was not released yet I target this for 1.609.2.

[jenkins-infra-bot]

albers:

• Original comment link
• Raw content of original comment:

  After this is released, I'll update the plugin's wiki page:
  
  However, for backwards compatibility purposes, subsequent core releases still bundle the (old) version.
  

After this is released, I'll update the plugin's wiki page:

However, for backwards compatibility purposes, subsequent core releases still bundle the (old) version.

[jenkins-infra-bot]

albers:

• Original comment link
• Raw content of original comment:

  updated the plugin page
  

updated the plugin page