> On 27 Feb 2019, at 19:25, wodel youchi wrote:
>
> Hi,
>
> What do you mean by : enable password-migration mode? can you elaborate,
> where do I have to enable it? on the master on the slave?
> On 28 Feb 2019, at 05:22, xinhuan zheng wrote:
>
> Hello,
>
> I have been struggling with this problem for a while. When a user changed
> their password, our 389 directory servers received new password and saved
> into directory server. However, when user tries to login to a server whose
> On 27 Feb 2019, at 23:41, Alberto Viana wrote:
>
> I'm facing a very similar problem, my version:
> 389-Directory/1.3.7.4.20170912git26a9426
>
> So, it's probably you right, maybe It's a 1.3.x problem.
It’s still a problem though. I just don’t have the setup to build/test 1.3.x
anymore.
Hello,
I have been struggling with this problem for a while. When a user changed their
password, our 389 directory servers received new password and saved into
directory server. However, when user tries to login to a server whose
authentication is using 389 directory server, their new password
I'm facing a very similar problem, my version:
389-Directory/1.3.7.4.20170912git26a9426
So, it's probably you right, maybe It's a 1.3.x problem.
In my case, I disabled the plugin until I can upgrade my 389 version.
On Fri, Feb 22, 2019 at 1:07 AM William Brown wrote:
> Okay, I did this with a
Hi,
What do you mean by : enable password-migration mode? can you elaborate,
where do I have to enable it? on the master on the slave?
In my previous post I did test changing the password using both clear an
pre-hashed password, and it didn't work.
2) Modify userPassword from the slave using*
