# Enable mapping of LDAP attributes to multiple user fields
**URL:** https://community.zammad.org/t/enable-mapping-of-ldap-attributes-to-multiple-user-fields/9509
**Category:** No implementation planned
**Tags:** duplicate
**Created:** [June 20, 2022, 10:11am UTC](https://community.zammad.org/t/enable-mapping-of-ldap-attributes-to-multiple-user-fields/9509 "2022-06-20T10:11:18Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@joules](https://community.zammad.org/u/joules)
#### Post date: [June 20, 2022, 10:11am UTC](https://community.zammad.org/t/enable-mapping-of-ldap-attributes-to-multiple-user-fields/9509/1 "2022-06-20T10:11:19Z")
### Infos:
- Used Zammad version: 5.1.1
- Used Zammad installation type: package
- Operating system: Debian 11
- Browser + version: all
- Used LDAP version: OpenLDAP 2.4.57+dfsg-3 (same version on zammad machine & remote server)
### Feature Request:
Hi,
in the LDAP integration configuration, i think it would be helpful if it was possible to map an LDAP attribute to more than one user field e.g. mapping the “mail” attribute of an LDAP user both to the “login” and “email” field of the corresponding zammad user.
Alternatively a warning message in the LDAP integration configuration dialog would be nice to notify the admin that mapping the same attribute to multiple zammad user fields is not possible.
### Current behaviour:
The configuration dialog for the LDAP integration lets the admin map an LDAP attribute to multiple zammad user fields but only one of those mappings is actually saved into the ldap\_config.
In my case the mapping “mail” =\> “email” got silently dropped in favour of the mapping “mail” =\> “login” which led to the problem described here:
> [@LDAP slow initial Sync](https://community.zammad.org/t/ldap-slow-initial-sync/9139):
>
> Infos: Used Zammad version: 5.1.1-1650894976.28c5b986.bullseye Used Zammad installation type: package Operating system: Debian 11 (bullseye) Browser + version: firefox.x86\_64 91.7.0-3.el7.centos Used MySQL version: 10.5.15-MariaDB-0+deb11u1 Used LDAP version: OpenLDAP 2.4.57+dfsg-3 (same version on zammad machine & remote server) Expected behavior: Initial LDAP sync completes in less than a few hours. Actual behavior: Initial LDAP sync takes \>=20 hours. Steps to reproduce the behavior: …
There exists another feature request for this, but it is closed:
> [@Confusion about LDAP attributes login & email](https://community.zammad.org/t/confusion-about-ldap-attributes-login-email/2343):
>
> Infos: Used Zammad version: 2.9.x Used Zammad installation source: docker-compose Operating system: Debian 9 Browser + version: Chrome Background I’ve configured the LDAP integration to create our agents. Zammad suggested this attribute mapping: LDAP givenname -\> Zammad Firstname LDAP sn -\> Zammad Lastname LDAP mail -\> Zammad Login I used it as suggested, but that caused our agents to be created with an empty email address: irb(main):278:0\> pp User.find\_by(login: 'firstname.lastname@ourco…
---
### Author:  [@system](https://community.zammad.org/u/system)
#### Post date: [August 11, 2023, 2:11am UTC](https://community.zammad.org/t/enable-mapping-of-ldap-attributes-to-multiple-user-fields/9509/2 "2023-08-11T02:11:51Z")
This topic was automatically closed after 416 days. New replies are no longer allowed.
---
### Author:  [@MrGeneration](https://community.zammad.org/u/MrGeneration)
#### Post date: [April 23, 2024, 9:11am UTC](https://community.zammad.org/t/enable-mapping-of-ldap-attributes-to-multiple-user-fields/9509/3 "2024-04-23T09:11:29Z")
I’m closing this feature request as duplicate in favor of [Confusion about LDAP attributes login & email](https://community.zammad.org/t/confusion-about-ldap-attributes-login-email/2343) as it has more drag.