Remove LDAP password hashing code

[Nathan Kinder]

Keystone currently has code that hashes LDAP user passwords when creating and updating users (using salted SHA-1). Keystone itself should not be doing this hashing. The LDAP server itself is supposed to receive the clear text "userPassword" attribute value so it can hash it itself. This hashing may or may not be using salted SHA-1 depending on the LDAP server implementation or password policy configuration. In addition, some LDAP server implementations may even refuse to accept pre-hashed passwords.

The proper behavior is to just pass the clear-text password off to the LDAP server as a part of the LDAP add or modify operation.

[Openstack Gerrit (openstack-gerrit)]

Fix proposed to branch: master
Review: https://review.openstack.org/88109

[Openstack Gerrit (openstack-gerrit)]

Reviewed: https://review.openstack.org/88109
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=c94d19b486a54eb889585ce03aac58d644a9599c
Submitter: Jenkins
Branch: master

commit c94d19b486a54eb889585ce03aac58d644a9599c
Author: Nathan Kinder <email address hidden>
Date: Wed Apr 16 16:21:25 2014 -0700

    Remove LDAP password hashing code

    Keystone should not be hashing passwords for LDAP users
    itself. Password hashing should be performed by the LDAP
    server, as password policies may not allow pre-hashed
    passwords to be set (they may enforce a scheme that is
    stronger that salted SHA-1).

    This removes the LDAP password hashing code. When using
    fakeldap for running unit tests, passwords will not be
    hashed. For this reason, the hashing tests are skipped
    for LDAP backends.

    Closes-bug: 1308793
    Change-Id: Ia0998b7fd8fb5d01b86a947d18b7e79fcffd1228