Please ignore my previous email, I have located this option and experiencing with it...
__________________________________________________
Paul Bedorf | Linux Administrator | Mosaic
O: 905.238.8058 x 6414 | M: 416.799.4028
mosaic.com
-----Original Message-----
From: Bedorf, Paul
Sent: Tuesday, October 06, 2015 10:02 AM
To: General discussion list for the 389 Directory server project.
Subject: RE: [389-users] 389 Server force user password expiry
Hi William, do you know where can I find this ' nsAccountLock ' attribute?
__________________________________________________
Paul Bedorf | Linux Administrator | Mosaic
O: 905.238.8058 x 6414 | M: 416.799.4028
mosaic.com
-----Original Message-----
From: 389-users-bounces(a)lists.fedoraproject.org
[mailto:389-users-bounces@lists.fedoraproject.org] On Behalf Of William Brown
Sent: Monday, October 05, 2015 7:03 PM
To: General discussion list for the 389 Directory server project.
Subject: Re: [389-users] 389 Server force user password expiry
On Mon, 2015-10-05 at 16:14 -0400, Rob Crittenden wrote:
Bedorf, Paul wrote:
> I am running a 389 Directory Server v1.2.9.9
>
> We have enabled a password policy as follows:
>
>
>
> However, I don’t want to wait until tomorrow for my ‘test’ user to
> expire, as im doing some API testing and need the ‘test’
>
> user to expire at any time. How would I force a user password expiry
> on an individual account?
>
A coarse way to do it is to manually advance the system clock. Or find
the attribute holding the expiration date and tweak it.
Set either nsAccountLock: true or change accountUnlockTime: to be in the future.
You can get the current DS system time for the root DSE, and just add to it.
--
William Brown <william(a)blackhats.net.au>
--
389 users mailing list
389-users(a)lists.fedoraproject.org
http://cp.mcafee.com/d/5fHCN8gdEIccnushud79KVJ5BNdBYQsK6QmhObyoVASyUed7ba...