After removing accounts from a group, the Synchronizer did not sync them as two single accounts. There is still one virtual account in the Conjur.
Is this expected behavior?
How could we synchronize two individual accounts not in the Group?
After removing accounts from the group, how do we get two accounts instead of one virtual account in the Conjur?
How could we remove the empty group from the Vault? (deleting the last account from the group, the group would not be removed)
Issue
Please provide instructions on how to split accounts (Dual Accounts) within a group back into individual accounts Case: We removed the accounts from the group, but Synchronizer did not sync them as 2 single accounts. There is still one virtual account in the Conjur. The questions are the next: 1. Is this expected behaviour? 2. How could we synchronize 2 individual accounts not in the Group? 3. After removing accounts from the group, how do we get 2 accounts instead of 1 virtual account in the Conjur? 4. How could we remove the empty group from the Vault? (We thought that by deleting the last account from the group, the group would also be removed)
Environment
Vault Conjur Synchronizer Documentation
Resolution
The rotational group setting is required for CPM to detect that accounts require a password change. This group however has absolutely no impact on Synchronizer - Synchronizer does not read it, doesn't know about its existence and does not indicate to Synchronizer that certain accounts are in dual account setup. Synchronizer recognizes dual accounts by the three attributes: - VirtualUserName - Index - DualAccountStatus. The logic is the next: - if an account has these three attributes (ALL three attributes must be there), it's recognized as a dual account - if those three attributes are not set, it's treated as a single account. So, answering to those questions: 1) Yes, this is expected behaviour. Accounts with attributes VirtualUserName, Index and DualAccountStatus are synced with VirtualUsername as an identifier (no need to be in a group but must have status Active). 2) To sync two individual accounts - do not set VirtualUserName, Index and DualAccountStatus attributes on them. 3) Removing accounts from the group has no impact on Synchronizer. You must remove the VirtualUserName, Index and DualAccountStatus attributes to sync them as two separate accounts. 4) Delete it via PAClient, for example
Steps
The rotational group setting is required for CPM to detect that accounts require a password change. This group, however, has absolutely no impact on Synchronizer - Synchronizer does not read it, doesn't know about its existence, and does not indicate to Synchronizer that certain accounts are in dual account setup. Synchronizer recognizes dual accounts by the three attributes: - VirtualUserName - Index - DualAccountStatus. The logic is the next: - if an account has these three attributes (ALL three attributes must be there), it's recognized as a dual account - if those three attributes are not set, it's treated as a single account. Answering to those initial mentioned questions: 1. Yes, this is expected behavior. Accounts with attributes VirtualUserName, Index, and DualAccountStatus are synced with VirtualUsername as an identifier (no need to be in a group, but must have status Active). 2. To sync two individual accounts - do not set VirtualUserName, Index, and DualAccountStatus attributes on them. 3. Removing accounts from the group does not impact Synchronizer. However, you must remove the VirtualUserName, Index, and DualAccountStatus attributes to sync them as two separate accounts. 4. Delete it via PAClient, for example.
View full article