Security Software

We are planning to turn on password policy to lock account after user failed to provide correct password after n times and the account will be lock forever unless administrator is to reset the password retry count.

We implemented password policy with role and cos so that the policy only imposed on end users but not administrators. The password policy works fine.

We understand that for DS 5.2 p.4, the password retry count is per instance, so the account lock is per instance. The problem we now encountered is at account unlock. We developed a function to reset the password retry count in order to unlock the account. It works fine in our test env. However, in production, we have 2 masters and 4 replicas and our replicas are all read only, all update is referred to the 2 masters. Now, when we update the master setting 0 to the password retry count, the reset is not populated to the replicas and when we try update the replica directly, the update get referred to the master and hence the attribute on the replica remains the same.

Is there a way to unlock the account that got locked at the read only replica?