Distributed Vaults (Active/Active)

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Distributed Vaults (Active/Active)

L3 Networker

Has anyone had luck with testing the high availability with Distributed Vaults? I have spent a few days in trying and replicating the failure scenarios. I have encountered a few hurdles with testing a specific use case when the master becomes unavailable. Here is what I have :

 

Vault A and Vault B setup as master and satellite respectively : Login works great. PVWA is able to communicate with the satellite vault and the write operations are redirected to the master. No issues at all - everything works fine.

 

Vault A (master) is shut down: Vault B (satellite) realises that the master is unavailable and prints out a log message indicating the same. There is also a message in the log that states that the vault has switched to read-only mode and that the user has to logout and login back in order to continue using PVWA.

 

This is where things go a little weird. It logs me out - which is good. But, when I try to re-login, I get the below message on the Sign In page:

CASW078E General authentication error, Failed to logon. Code=-1

At this point PVWA is completely unavailable. Although AIM agents are still able to communicate with the satellite Vault, but aren't able to change their passwords since the vault is read-only. - which is OK. Restarting the PVWA makes it clock and the login page doesn't even show up.

 

Here is how my Vault.ini looks:

VAULT = "CAMainVault" ADDRESS= Vault A, Vault B PORT=1858   DistributedVaults=Static

 

Has anyone been able to get this to work? Unfortunately, there is not enough documentation or prior cases available on t-shooting issues related to distributed vaults, which may be because the concept is relatively new.

 

3 REPLIES 3

L4 Transporter

In the use case you are testing, i am in the assumption that you have not prompted the Satellite to Master, and you are expecting a specific result? If so can you explain what is the expected result?

 

I dont know whether you had a read of this?;

https://docs.cyberark.com/Product-Doc/OnlineHelp/PAS/Latest/en/Content/PASIMP/Distributed-Vaults-dur...

L3 Networker

@Rahel Ahmed​ : Per the documentation link that you provided and that I have referred to in the past :

"PVWA users will have read-only access to their assets, and will be notified when connectivity to the Primary Vault is restored. After connectivity to the Primary Vault is restored, users must log on to their local PVWA to restore write operations."

I am expecting that when there is no Master in the DA environment, the satellite should be able to operate in the read only mode without being promoted to Master. This benefits PVWA users to login and checkout the passwords, but they will not allow them to make any updates (such as adding new accounts).

 

L0 Member

Faced exactly same issue and error.

 

Solved by adding:

 

<appSettings>

<add key=”SessionMustHaveMaster” value=”no” />

</appSettings>

 

To C:\inetpub\wwwroot\PasswordVault\web.config on PVWA and restarting IIS.

It is described here.

  • 2147 Views
  • 3 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!