Currently, DSLdapObject supports only single-valued RDN. We should support the multi-valued options too (i.e. dnaHostname=ldap1.example.com+dnaPortNum=389,cn=Account UIDs,ou=Ranges,dc=example,dc=com) It is a rare feature but still, it should be implemented. It is used at least once in DNA shared config entries.
dnaHostname=ldap1.example.com+dnaPortNum=389,cn=Account UIDs,ou=Ranges,dc=example,dc=com
python-ldap Distinguished Name handling can be used for the situation. https://www.python-ldap.org/en/latest/reference/ldap-dn.html
Metadata Update from @mreynolds: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Issue set to the milestone: 1.4.1
Metadata Update from @mreynolds: - Issue set to the milestone: 1.4.0 (was: 1.4.1)
Metadata Update from @mreynolds: - Issue priority set to: minor - Issue set to the milestone: 1.4.3 (was: 1.4.0)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/3329
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.