Skip to content

LDAP mapper AD altSecurityIdentities support.#85

Open
guitarmanusa wants to merge 2 commits intoOpenSC:masterfrom
guitarmanusa:ldap_AD_support
Open

LDAP mapper AD altSecurityIdentities support.#85
guitarmanusa wants to merge 2 commits intoOpenSC:masterfrom
guitarmanusa:ldap_AD_support

Conversation

@guitarmanusa
Copy link

In large, Windows first organizations, Active Directory does not store the full binary certificate. Rather it stores the IssuerDN and certificate serial number in the attribute altSecurityIdentities. This feature allows large organizations to use ldap mapper to map the certificate serial number and Issuer to the pre-existing AD user attributes without having to create massive map files or make any other additional changes.

Kyle Francis added 2 commits December 10, 2025 16:17
Adds a new mapping mode to the LDAP mapper to support Microsoft Active
Directory's `altSecurityIdentities` attribute.

This mode is enabled by setting the `use_alt_security_identities`
option to `true` in the `ldap_mapper` configuration block.

When enabled, the mapper will:
1. Extract the Issuer DN and Serial Number from the certificate.
2. Format them into the AD-specific string:
   `X509:<I>IssuerDN<SR>SerialNumber`
3. Use this string to find a matching user entry by searching the
   configured `attribute` (which should be set to
   `altSecurityIdentities`).

This allows for certificate-based authentication in a typical AD
environment where `userCertificate` binary comparison is not used.
…nstructs a filter using AD styled altSecurityIdentities="X509<I>IssuerDN<SR>Serial" to enable ldap_mapper to correctly match a validated certificate to an AD user entry. AD does not store the certificate in binary, making this query necessary in Windows first environments.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant