At server startup the server tries to convert any DES passwords to AES. But if a defined backend does not have any entries(err=32) when this process quits and it stops trying to convert DES passwords. It should continue to try all the backends, even if it encounters an error.
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1320715
attachment 0001-Ticket-47888-DES-to-AES-password-conversion-fails-if.patch
Looks good to me.
83f3f44..6b7f980 master -> master commit 6b7f980 Author: Mark Reynolds mreynolds@redhat.com Date: Thu Mar 24 09:46:11 2016 -0400
718bcf2..c6eaf69 389-ds-base-1.3.4 -> 389-ds-base-1.3.4 commit c6eaf69
Added CI test
6b7f980..afb1e33 master -> master commit afb1e33
c6eaf69..957dfe1 389-ds-base-1.3.4 -> 389-ds-base-1.3.4 commit 957dfe1
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1376558
Metadata Update from @mreynolds: - Issue assigned to mreynolds - Issue set to the milestone: 1.3.4.10
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/1837
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.