We are delighted to share our new EIC Delivery Methodology for efficiently managing Saviynt Implementations and delivering quick time to value. CLICK HERE.

Migrate vault from old tenant (v23.5) to a new instance of the internal tenant (v23.11)

vidyaa
New Contributor II
New Contributor II

Background:

We have an internal tenant for our organization and have been working on deploying the CPAM module. We had completed the setup of a HashiCorp Vault on it. Recently, we received access to the new instance of the tenant (v23.11) and would like to migrate the vault to the new tenant. Is there a way to do that? If so, how? Or do we need to recreate the vault on the new upgraded instance?

5 REPLIES 5

NageshK
Saviynt Employee
Saviynt Employee

@vidyaa Thanks for posting your question. Few questions before we can determine if the migration has to be done or not. 

  1. Is the new version of EIC (23.11) hosted internally as well? Or is it SaaS?
  2. Have you migrated the endpoints, connections and all other required saviynt objects from 23.5 setup to 23.11? Essentially, are the endpoint and connection names the same in 23.5 and 23.11 setups?
  3. How many credentials (ballpark) are in scope for migration?

In these situations, it is ideal to maintain the existing data (connections, endpoints, Sec Systems, etc.) so that existing vault url and setup could be re-used without the need for any migration. 

Thanks,

Nagesh K

vidyaa
New Contributor II
New Contributor II

Thank you @NageshK for your prompt response. To address your questions:

  1. It is SaaS and is not hosted on our internal network.
  2. We do not have intentions to migrate any of the existing connections, other than the vault. Our strategy involves rebuilding all other connections within the v23.11 environment.
  3. There are no specific credentials we are looking to migrate.

Given this information, could you kindly provide guidance on how we can efficiently reuse the credential vault and establish it within our new environment? Your assistance would be greatly appreciated.

Thank you!

NageshK
Saviynt Employee
Saviynt Employee

@vidyaa Thanks for the info. If you are not looking to migrate any specific credentials and also not planning to migrate the connections and endpoints, why do you need to reuse the vault from 23.5 version? 

Thanks

Nagesh K

vidyaa
New Contributor II
New Contributor II

@NageshK thanks for your feedback. I am trying to understand if we need to migrate the vault, at all. Or do we just reuse our current vault url and tokens to establish a new connection. I am assuming the latter from your replies.

NageshK
Saviynt Employee
Saviynt Employee

@vidyaa sorry for the dealy in response. Yes, as you do not have anything specific to bring over from existing setup, you can use either the vault that comes with the new EIC setup (23.11 setup). This will be a cleaner implementation. 

Thanks,

Nagesh K