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
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 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
indivi
Hi Rich, List
after a re- initialization this am of both ldap2 , 4 start seeing the
following error , after some research seems this is a know issues (?)
Do I need to re-write the replication agreement to avoid this
error/warning, the content of DS seems do not work properly for memberOF
On 10/05/2015 08:57 AM, ghiureai wrote:
Gmorning List and Rich,
I manged some progress Friday with cfg multimaster replication
fractional ( exclude memberOf plugin) the final goal is to have 3
ldap 's aka : 1,2 and 4 in mutlimaster fraction rep.
I had cfg dlap 2 to 4 as mutimaster , now
Gmorning List and Rich,
I manged some progress Friday with cfg multimaster replication
fractional ( exclude memberOf plugin) the final goal is to have 3 ldap
's aka : 1,2 and 4 in mutlimaster fraction rep.
I had cfg dlap 2 to 4 as mutimaster , now I would like to bring in
ldap1 in cfg (
