[JENKINS-42288] Expose LDAP custom attributes as (environment) variables

Nobody has claimed this yet.

With ldap-plugin and build-user-vars-plugin we can get the jenkins user names and email from LDAP attributes, as environment variables (highly useful for Slack notifications for example).

However, it would be even better to be able to expose any custom LDAP attribute as environment variables (the list of LDAP attributes and maybe also the mapping to env vars would be configurable).

A use-case: If we store in LDAP the Slack username, we could then send the correct Slack username in the notification.

---
Originally reported by trsystran, imported from: Expose LDAP custom attributes as (environment) variables

• status: Open
  
• priority: Minor
  
• component(s): ldap-plugin
  
• resolution: Unresolved
  
• votes: 1
  
• watchers: 2
  
• imported: 2025-12-09
  

Raw content of original issue

With ldap-plugin and build-user-vars-plugin we can get the jenkins user names and email from LDAP attributes, as environment variables (highly useful for Slack notifications for example).


However, it would be even better to be able to expose any custom LDAP attribute as environment variables (the list of LDAP attributes and maybe also the mapping to env vars would be configurable).


A use-case: If we store in LDAP the Slack username, we could then send the correct Slack username in the notification.

Review the ldap-plugin entry points that currently expose Jenkins user names and email, along with the related build-user-vars-plugin behavior. Determine how a configurable list of LDAP attributes and their environment-variable mapping should work; done means a configured custom attribute, such as a Slack username, is available as an environment variable.

Written by the indexing model from the issue text.