Add multivalued RDN support to lib389 API

[389-ds-bot]

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/50270

• Created at 2019-03-08 12:12:26 by spichugi (@droideck)
• Assigned to nobody

---

Issue Description

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.

python-ldap Distinguished Name handling can be used for the situation. https://www.python-ldap.org/en/latest/reference/ldap-dn.html

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2019-04-04 17:40:18

Metadata Update from @mreynolds389:

• Custom field origin adjusted to None
• Custom field reviewstatus adjusted to None
• Issue set to the milestone: 1.4.1

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2019-04-04 17:40:29

Metadata Update from @mreynolds389:

• Issue set to the milestone: 1.4.0 (was: 1.4.1)

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2020-02-12 16:35:38

Metadata Update from @mreynolds389:

• Issue priority set to: minor
• Issue set to the milestone: 1.4.3 (was: 1.4.0)