During development of PLAIN and LDAPSSOTOKEN mechanisms, a number of issues were found with lib389 handling of SSL, the sasl mechanisms, and the extended operations. This fixes those issues.
attachment 0001-Ticket-48707-Implement-draft-wibrown-ldapssotoken-01.patch
Your patch looks good to me and all tests are passed. Ack.
One thing only. I am not sure that I fully understand a usage process. Can you please explain the benefit from this commit in more detailed way with some example or add a test case to lib389/tests?
Ahhh, the tests will be coming with a commit to dirsrv. They are testing our sasl mechanisms. I'll be sure to ping you when I upload it.
commit b9a07e29a56466207ecf7dc7e342596f5fd4fa50 Total 11 (delta 7), reused 0 (delta 0) To ssh://git.fedorahosted.org/git/389/lib389.git f97cf65..b9a07e2 master -> master
Metadata Update from @spichugi: - Issue assigned to firstyear - Issue set to the milestone: 0.0 NEEDS_TRIAGE
Metadata Update from @vashirov: - Issue set to the milestone: None (was: 0.0 NEEDS_TRIAGE)
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/2115
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.