nsslapd-dn-validate-strict right now is either on or off. We have allowed too many invalid DNs for too long to be able to run with strict checking on all the time. We need to have different levels of checking. At least these two: warn - warn when there is an invalid DN, but allow; allowspaces - allow DNs when the only problem is the space after the comma before the next RDN, but reject all other DNs; warnspaces - warn when there is an invalid DN, except when the only problem is the space after the comma before the next RDN - in that case, just silently allow the DN.
Metadata Update from @rmeggins: - Issue set to the milestone: FUTURE
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/882
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.