How to manage database dependent accounts

Hi,

I have a customer that wants to manage replicas of databases and accounts;

  • These databases are replicas or essentially copies of each other;
  • the accounts and passwords are then the same for each replica;
  • the accounts are local and not directory accounts

For example, there are two MySQL databases A and B and are essentially a copy of each other.

  1. How do we onboard A and B and specify that account 'Shared' is a dependent account for both A and B?
  2. How do we ensure that if we reset the password for Shared that the password will be set and be the same on A and B?

Kind regards,

Noriel

Parents
  • Hi Noriel,

    How are the passwords kept in sync at the moment? 

    If you change the password manually on Database A does it auto replicate to Database B?

    If so then SPP would only have to change it on one Database and let the DB replication handle the sync is one scenario.

    Otherwise, you can also test using Password Sync Groups feature in SPP where you can add two accounts in a group and have SPP set the same password for both.

    More on Password Sync Groups can be found here:

    support.oneidentity.com/.../110

    Thanks!

  • Hi Tawfiq,

    1. At the moment, only database A and account is on boarded; the account is then password managed.
    2. IF the password is changed on database A account, then Yes, the password is auto replicated to database B
    3. The problem is if Safeguard changes the database A account password, how then will Safeguard know to also match the password for database B account and not change it again?
    4. This is an interesting feature, however database B could be read only. Also, even if it weren't the database may employ password history which would prevent the Password Sync Group from resetting lower priority accounts in the password sync group

    Kind regards,

    Noriel

Reply
  • Hi Tawfiq,

    1. At the moment, only database A and account is on boarded; the account is then password managed.
    2. IF the password is changed on database A account, then Yes, the password is auto replicated to database B
    3. The problem is if Safeguard changes the database A account password, how then will Safeguard know to also match the password for database B account and not change it again?
    4. This is an interesting feature, however database B could be read only. Also, even if it weren't the database may employ password history which would prevent the Password Sync Group from resetting lower priority accounts in the password sync group

    Kind regards,

    Noriel

Children