Set passwordUserAttributes to "cn uid givenname" using ldapmodify or dsconf
Check audit log:
dn: cn=config result: 0 changetype: modify replace: passwordUserAttributes passwordUserAttributes: cn uid givenname
Restart server and check dse.ldif:
passwordUserAttributes: cn uid givenname
But... ldapsearch shows:
... passwordUserAttributes: cn passwordUserAttributes: uid passwordUserAttributes: givenname ...
Metadata Update from @mreynolds: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Issue priority set to: critical - Issue set to the milestone: 1.4.1
Metadata Update from @mreynolds: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1816857
Metadata Update from @spichugi: - Issue assigned to spichugi
https://pagure.io/389-ds-base/pull-request/51012
a252a6f..36c593d master -> origin/master 21638c0..0b88633 389-ds-base-1.4.1 -> 389-ds-base-1.4.1 b213ed4..24c501d 389-ds-base-1.4.2 -> 389-ds-base-1.4.2
Metadata Update from @spichugi: - Issue close_status updated to: fixed - 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/3928
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 (was: fixed)
Login to comment on this ticket.