When unhashed password are generated (nsslapd-unhashed-pw-switch: on) , unhashed value is present in the replication changelog and also in the retroCL (if it is enabled). The option 'nolog' prevents to log it into replication changelog and retroCL.
It would more convenient to have a 'on_log_replCL'
So the options are
all version
testcase to be provided
when nsslapd-unhashed-pw-switch: on, unhashed password is present in both retro CL and replication CL
when nsslapd-unhashed-pw-switch: on_log_repl, unhashed password is present only in replication CL
attached testcase
Metadata Update from @tbordaz: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None
PR https://pagure.io/389-ds-base/pull-request/50075
Metadata Update from @mreynolds: - Issue set to the milestone: 1.4.1
Metadata Update from @mreynolds: - Issue priority set to: minor - Issue set to the milestone: 1.4.3 (was: 1.4.1)
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/3129
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)