+++ This bug was initially created as a clone of Bug #741999 +++
I have tried to use a SASL/PLAIN bind in order to do binds with a user id that is not a DN.
Because SASL mappings can resolve an arbitrary uid into a DN I was hoping to use that to bind to a directory where anonymous searches are disabled (therefore the client can't use an anonymous bind to search the DN itself.
Unfortunately it appears the current DS code is not able to perform SASL/PLAIN authentication. Sasl mapping is incorrectly performed. It happens twice, the first time it properly maps the provided user name to a DN the second time it tries to map the found DN again as if it were a user name.
Rich says DS may no be able to properly provide SASL with callback to handle checking the password.
will need steps to reproduce/verify this issue
This is not needed for 6.3. Moving forward to 6.4.
please add steps to verify this issue
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
This request was erroneously denied for the current release of Red Hat Enterprise Linux. The error has been fixed and this request has been re-proposed for the current release.
Test automated :: trac27 in ldapi test suite
400|0 19 1 22:33:39|IC Start
200|0 19 22:33:39|TP Start
520|0 19 18906 1 1|LDAPI TEST 19: SASL PLAIN over ldapi
520|0 19 18906 1 2|Search by "uid=ldapi_user0,o=ldapi.net" with SASL PLAIN mech: Success
520|0 19 18906 1 3|TestCase [trac27] result-> [PASS]
520|0 19 18906 1 4|Deleting passwordStorageScheme failed: 53
520|0 19 18906 1 5|TestCase [trac27] result-> [PASS]
220|0 19 0 22:33:40|PASS
410|0 19 1 22:33:40|IC End
version :: 89-ds-base-18.104.22.168-8.el6
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.