https://bugzilla.redhat.com/show_bug.cgi?id=644089
Description of problem: " SASL proxy authorization is not supported in Directory Server; therefore, Directory Server ignores any SASL authzid value supplied by the client. " Not in RHDS http://www.centos.org/docs/5/html/CDS/ag/8.0/Introduction_to_SASL-SASL_Identity _Mapping.html " NOTE SASL proxy authorization is not supported in Directory Server; therefore, Directory Server ignores any SASL authzid value supplied by the client. " This feature exists in OpenLdap: http://www.openldap.org/doc/admin24/sasl.html 15.3. SASL Proxy Authorization Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
batch update moving tickets to future
set default ticket origin to Community
Added initial screened field value.
Correcting source to match reality.
Metadata Update from @rmeggins: - Issue set to the milestone: FUTURE
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to None (was: Needs Review) - Issue close_status updated to: None - Issue set to the milestone: 1.4.4 (was: FUTURE)
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/199
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)
Login to comment on this ticket.