Okay. At this point I need to duplicate the configuration to diagnose the issue
further, but I don’t have much time to do so.
An alternate, can you use a read only replica with referral’s enabled instead?
> On 1 Mar 2019, at 00:13, wodel youchi wrote:
>
> Hi,
>
> I did a test using
Hi,
I did a test using ldappasswd, and it didn't work, I didn't get any error
message from the CLI, and the $? variable returned 0, but the password has
not been changed.
After issuing the command I tried an ldapsearch with the Adam user using
the new-password and it didn't work "Invalid
> 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?
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*
> On 26 Feb 2019, at 00:23, wodel youchi wrote:
>
> 3) Modify userPassword from the slave using encrypted password
> ldapmodify -h localhost -p 389 -D "uid=lnadmin,ou=special
> users,dc=example,dc=com" -w wolverine -x < dn: uid=adam,ou=people,dc=example,dc=com
> changetype: modify
>
Hi,
I redid the configuration from scratch, and I've created a new user
(uid=lnadmin,ou=special users,dc=example,dc=com) and I gave him
administrative rights.
This new user belongs to the chained area.
I did some tests with this account to modify users attributes including the
userPassword
> On 19 Feb 2019, at 00:54, Mark Reynolds wrote:
>
>
>
> On 2/18/19 7:46 AM, wodel youchi wrote:
>> Hi,
>>
>> I did a test, but unfortunately it didn't work for me.
>>
>> This is my LAB:
>> • 389DS Servers :
>> • OS CentOS7 all updates
>> • 389DS version
On 2/18/19 7:46 AM, wodel youchi wrote:
Hi,
I did a test, but unfortunately it didn't work for me.
This is my LAB:
* 389DS Servers :
o OS CentOS7 all updates
o 389DS version 1.3.8.4-22
o domain : dc=example,dc=com
o users on : uid=%u,ou=people,dc=example,dc=com
Hi,
I did a test, but unfortunately it didn't work for me.
This is my LAB:
- 389DS Servers :
- OS CentOS7 all updates
- 389DS version 1.3.8.4-22
- domain : dc=example,dc=com
- users on : uid=%u,ou=people,dc=example,dc=com
- One master server (idm01.example.com)
I don’t see any reason why it wouldn’t still work today? It would be good if
you were able to test a development deployment and let us know the results and
processes taken?
> On 17 Feb 2019, at 21:48, wodel youchi wrote:
>
> Hi,
>
> We have a master 389DS Server, and several Slaves.
>
>
10 matches
Mail list logo
