On Fri, May 29, 2015 at 2:13 AM, David Paulsen <[email protected]> wrote:
> I'm running in to a strange issue. I have two separate servers running the > official 2.0.0-M20 release. In one instance I can change the password to > anything I want (including the same password) when I bind to the > connection using the built in admin user (dn=uid=admin,ou=system). In > another instance running the same version of the 2.0.0-M20 release, that > exact same operation (again bound as admin user) results in the following > error: invalid reuse of password present in password history > you sure that this is happening during bind? this check is performed only while updating the password of a user (excluding admin user) > > It should never enforce the password policy for the admin user, correct? > Any idea what could be causing it to enforce the policy in one M20 > instance and not the other? > > Thanks! > > -- Kiran Ayyagari http://keydap.com
