Thread-topic: [389-users] Re: How to replicate password lockout attributes from a consumer or hub to a master(s)
From: Michael Starling <mlstarling31@xxxxxxxxxxx> Sent: Monday, August 16, 2021 10:54 AM To: Pierre Rogier <progier@xxxxxxxxxx>; General discussion list for the 389 Directory server project. <389-users@xxxxxxxxxxxxxxxxxxxxxxx> Subject: [389-users] Re: How to replicate password lockout attributes from a consumer or hub to a master(s)
From: Pierre Rogier <progier@xxxxxxxxxx> Sent: Monday, August 16, 2021 6:33 AM To: General discussion list for the 389 Directory server project. <389-users@xxxxxxxxxxxxxxxxxxxxxxx> Cc: Michael Starling <mlstarling31@xxxxxxxxxxx> Subject: Re: [389-users] Re: How to replicate password lockout attributes from a consumer or hub to a master(s)
From: Michael Starling
<mlstarling31@xxxxxxxxxxx> Sent: Friday, August 13, 2021 10:41 AM To: Mark Reynolds <mreynolds@xxxxxxxxxx>; General discussion list for the 389 Directory server project.
<389-users@xxxxxxxxxxxxxxxxxxxxxxx> Subject: Re: [389-users] How to replicate password lockout attributes from a consumer or hub to a master(s)
From: Michael Starling
<mlstarling31@xxxxxxxxxxx> Sent: Thursday, August 12, 2021 3:29 PM To: Mark Reynolds <mreynolds@xxxxxxxxxx>; General discussion list for the 389 Directory server project.
<389-users@xxxxxxxxxxxxxxxxxxxxxxx> Subject: Re: [389-users] How to replicate password lockout attributes from a consumer or hub to a master(s)
From: Mark Reynolds
<mreynolds@xxxxxxxxxx> Sent: Thursday, August 12, 2021 3:16 PM To: Michael Starling
<mlstarling31@xxxxxxxxxxx>; General discussion list for the 389 Directory server project.
<389-users@xxxxxxxxxxxxxxxxxxxxxxx> Subject: Re: [389-users] How to replicate password lockout attributes from a consumer or hub to a master(s)
I've taken over a large 389-ds environment running on Oracle Linux 8 and the first task I need to complete is to enable password lockouts.
I was able to enable password lockouts successfully however it only works if the client is pointed directly to a master. The account locks out and the attributes are propagated down to the hubs and consumers.
If the client is pointed to a read-only hub or consumer then the account does not lockout and the password attributes do not propagate back to the masters.
passwordIsGlobalPolicy: on is set on all masters, hubs and consumers
Password policy attributes I expect to replicate:
passwordRetryCount
accountUnlockTime
retryCountResetTime
I've tried following the chaining guide below which I think is what I need to do to get this work as expected, however I've hit a snag.
Introduction. The usual deployment for a large replication topology will have the client applications reading from hubs or dedicated consumers in order to spread out the load and off-load search request
processing from the masters.
The document states the backend must be added to the hub or consumer, however when I try and add the following LDIF to the hub I get the "unwilling to perform" error.
This makes sense because the hub is read-only so I'm confused as how I can update the config on a read-only hub or consumer?
Hi Michael,
To complete Mark's answer and try to solve your confusion:
hub and consumer are read-only replicas (i.e backends)
cn=config is another backend that is still writable.
So you should not be able to modify the entries in the replicated suffix (
and should instead get referrals towards the master(s)) but you should still be able to modify the config.
Regards,
Pierre
Hi Pierre.
Thanks for confirming what I'm seeing.
Any idea how to set multiple values in the nsfarmserverurlattribute?
adding new entry "cn=chainlab,cn=chaining database,cn=plugins,cn=config"
ldap_add: Server is unwilling to perform (53)
This is the doc you want to follow to get this working. But it is complicated...
In this case I'm not sure why the error 53 is being returned. There is something about that entry it does not like. So please check the access and errors log from the time of this failure (see /var/log/dirsrv/slapd-YOUR_INSTANCE/). There is usually more
info logged when an error 53 happens.
Also what version of 389-ds-base are you running?
Thanks,
Mark
Hub or Consumer
Step 1 (Hub and Consumer): the chaining backend must be created on the hub and consumer:
dn: cn=chainbe1,cn=chaining database,cn=plugins,cn=config
objectclass: top
objectclass: extensibleObject
objectclass: nsBackendInstance
cn: chainbe1
nsslapd-suffix: <suffix to replicate>
nsfarmserverurl: ldap://supplier1:port supplier2:port ... supplierN:port/ # also, ldaps can be used instead
# of ldap for secure connections -
# requires the secure port
nsmultiplexorbinddn: cn=Replication Manager,cn=config # or whatever the replica bind DN is on the supplier
nsmultiplexorcredentials: password
nsCheckLocalACI: on
Ok, I think its not liking the multiple values in the attribute, even though the document says you have multiple urls. I think you need to add the config like this:
