Sample DN syntax secretary: cn=CN0+bogus0=BOGUS0,ou=OU0,ou=OU1,dc=example+bogus1=BOGUS1,dc=com
Although bogus0 nor bogus1 are defined in the schema, the server accepts the value. $ ldapmodify ... dn: uid=test_user,dc=example,dc=com changetype: modify replace: secretary secretary: cn=CN0+bogus0=BOGUS0,ou=OU0,ou=OU1,dc=example+bogus1=BOGUS1,dc=com
modifying entry "uid=test_user,dc=example,dc=com"
$ egrep bogus /etc/dirsrv/slapd-/schema/.ldif $
Metadata Update from @nhosoi: - Issue set to the milestone: 1.3.6 backlog
Metadata Update from @mreynolds: - Issue close_status updated to: None - Issue set to the milestone: FUTURE (was: 1.3.6 backlog)
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to None - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
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/1627
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.
Login to comment on this ticket.