Reference16r1:Configure OpenLDAP Directory Replication: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
|||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
==Applies To== | ==Applies To== | ||
* innovaphone PBX 16r1beta2 | |||
* Tested with OpenLDAP slapd-Version: 2.4.57 | |||
==More Information== | |||
=More Information= | |||
With version 16, we have enhanced the LDAP replication functionality for Active Directory, allowing OpenLDAP to be used as a source as well. | With version 16, we have enhanced the LDAP replication functionality for Active Directory, allowing OpenLDAP to be used as a source as well. | ||
| Line 11: | Line 10: | ||
All other attribute mappings can be applied in the same way as they are for Active Directory replication. | All other attribute mappings can be applied in the same way as they are for Active Directory replication. | ||
==Related articles== | |||
[[Reference15r1:Configure_Active_Directory_Replication#Attribute_Mapping]] | |||
Latest revision as of 16:15, 29 October 2025
Applies To
- innovaphone PBX 16r1beta2
- Tested with OpenLDAP slapd-Version: 2.4.57
More Information
With version 16, we have enhanced the LDAP replication functionality for Active Directory, allowing OpenLDAP to be used as a source as well.
Unlike Active Directory, OpenLDAP does not have an objectGuid attribute; therefore, we use the entryUUID attribute as the source for our internal guid.
All other attribute mappings can be applied in the same way as they are for Active Directory replication.
Related articles
Reference15r1:Configure_Active_Directory_Replication#Attribute_Mapping