There was already a JIRA issue for this issue, I just added a comment to
the existing issue.
https://issues.apache.org/jira/browse/DIRSERVER-2067
On Sat, May 7, 2016 at 1:31 PM, Kiran Ayyagari wrote:
> Hal,
>
> This is a known issue and I initially thought was fixed in
Hal,
This is a known issue and I initially thought was fixed in trunk but
looks like it wasn't.
Please follow the steps mentioned in this message
http://markmail.org/message/rohhcxnar4ysfzlq
This will let you reset the password for now.
On Sat, May 7, 2016 at 5:30 AM, Hal Deadman
Le 07/05/16 02:00, Hal Deadman a écrit :
> I was able to recreate the issue with a test instance.
>
> I created a fresh instance of M21 directory using M10 studio. I set
> password expiration on password policy to some number, turned off grace
> logins, and changed the password of the admin user.
I was able to recreate the issue with a test instance.
I created a fresh instance of M21 directory using M10 studio. I set
password expiration on password policy to some number, turned off grace
logins, and changed the password of the admin user. I reconnected with the
new password, and set the
Although my server is running M21, the config might have come from a
slightly older release so if the changes to make the policy not apply to
admin require some additional configuration item then maybe I am missing
that.
I suppose creating a fresh instance on M21 and then back-dating the
I am using M21 and it doesn't appear to be bypassing the policy, at least
when it comes to password expiration.
The admin password had expired on both servers but I was able to login to
the backup server b/c grace logins were allowed. It did record a grace
login on the admin user when I logged
Le 03/05/16 18:50, Hal Deadman a écrit :
> I have a replicated directory in my dev lab where the admin user has an
> expired password on one of the two servers. Since I can't login as admin,
> how might I go about resetting the password on that user short of
> re-creating the instance?
the