diff options
| author | Rich Megginson <rmeggins@redhat.com> | 2006-02-15 21:22:46 +0000 |
|---|---|---|
| committer | Rich Megginson <rmeggins@redhat.com> | 2006-02-15 21:22:46 +0000 |
| commit | 191bf22c1f01d96e89b6359722580e9581506475 (patch) | |
| tree | 0514929ba358cb71ea71de508caf9e2ec39349fc /include | |
| parent | 92a9ca8975f64a89e5b1dfe569dce38b0ffb5f25 (diff) | |
Bug(s) fixed: 181587
Bug Description: Password Modify LDAPv3 extended operation erroneously
forces the client to supply old password
Reviewed by: Pete & Nathan (Thanks!)
Fix Description: If the BIND operation was successful, the CONN_DN field
is always set to the proper DN. This is even the case during a SASL or
client cert DN if the authentication was successful AND the given
identity could be mapped to a real user in the directory. Also, the
authmethod will be something other than NULL or none. So, if the old
password was not given, that is ok if there is a non-anonymous bind DN
and a real authmethod. The rest of the operation passes through the usual access control.
Platforms tested: Fedora Core 4
Flag Day: no
Doc impact: no
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions