[GH-ISSUE #927] [BUG] LDAP Property Mappings not propagated to LDAP Outpost #338

New issue

Closed

opened 2026-02-27 08:16:45 +03:00 by kerem · 1 comment

kerem commented

2026-02-27 08:16:45 +03:00

Owner

Originally created by @mpaluch92 on GitHub (Jul 3, 2024).
Original GitHub issue: https://github.com/lldap/lldap/issues/927

Deployment Info

Docker-Compose
LDAP-Outpost automatically set up by Authentik
Authentik-Version: 2024.6.0

Describe the bug
LDAP Property Mappings (for example to set the object field givenname based on the request.user.name field) are not set in the LDAP Outpost.

To Reproduce
Steps to reproduce the behavior:

Go to Customization -> Property Mappings and create a LDAP Property Mapping. For example:

Name: extract_last_name
Object field: sn

Expression:

 def get_last_name():
         name_parts = request.user.name.split()
         if len(name_parts) > 1:
             return name_parts[-1]
         else:
             return "N/A"

 return {"sn": get_last_name()}

Perform a query using ldapsearch.
See that the object field sn is not updated using the LDAP Property Mapping. However, testing the LDAP Property Mapping via GUI yields the correct value for the object field sn.

Expected behavior
When defining LDAP Property Mappings, the LDAP Outpost should show the LDAP Property Mappings as well.

Additional context
The integration docs for Snipe-IT also tell us to define LDAP Property Mappings for LDAP-Synchronization to work in Snipe-IT. However, I am currently stuck at this progress and cannot integrate my users into Snipe-IT.

Originally created by @mpaluch92 on GitHub (Jul 3, 2024). Original GitHub issue: https://github.com/lldap/lldap/issues/927 **Deployment Info** - Docker-Compose - LDAP-Outpost automatically set up by Authentik - Authentik-Version: `2024.6.0` **Describe the bug** LDAP Property Mappings (for example to set the object field `givenname` based on the `request.user.name` field) are not set in the LDAP Outpost. **To Reproduce** Steps to reproduce the behavior: 1. Go to `Customization` -> `Property Mappings` and create a `LDAP Property Mapping`. For example: - Name: `extract_last_name` - Object field: `sn` - Expression: ```python def get_last_name(): name_parts = request.user.name.split() if len(name_parts) > 1: return name_parts[-1] else: return "N/A" return {"sn": get_last_name()} ``` 2. Perform a query using `ldapsearch`. 3. See that the object field `sn` is not updated using the LDAP Property Mapping. However, testing the LDAP Property Mapping via GUI yields the correct value for the object field `sn`. **Expected behavior** When defining LDAP Property Mappings, the LDAP Outpost should show the LDAP Property Mappings as well. **Additional context** The integration docs for Snipe-IT also tell us to define [LDAP Property Mappings](https://docs.goauthentik.io/integrations/services/snipe-it/#authentik-property-mapping) for LDAP-Synchronization to work in Snipe-IT. However, I am currently stuck at this progress and cannot integrate my users into Snipe-IT.