https://bugzilla.redhat.com/show_bug.cgi?id=701803
Description of problem: On 05/03/2011 02:45 PM, Rich Megginson wrote: We could change it to use access control instead. That is, we could provide a default aci (targetattr=userPassword) (allow write .... ssf >= 56 ....) or something like that. Then, by default it would require a secure connection, but the user could change the aci.
commit changeset:5593a5f/389-ds-base Author: Nathan Kinder nkinder@redhat.com Date: Fri Oct 2 13:47:38 2009 -0700
Add ssf bind rule to access control plug-in. This patch adds a new ssf bind rule keyword to the access control plug-in. This allows you to write ACIs that require a specific level of encryption for the rule to apply. The new keyword can be used with '=', '!=', '<', '>', '<=' and '>=' comparators. I added code that stores the SSF in effect for an operation into the operation struct. The value that we store is the higher of the two between the SASL SSF and the SSL/TLS SSF.
already fixed in 1.2.9
Added initial screened field value.
Metadata Update from @rmeggins: - Issue assigned to rmeggins - Issue set to the milestone: 1.2.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/195
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.