I have an AD source in a segregated network. The app team is not maintaining a lower environment. Therefore I had to connect with the PROD app from the sandbox ISC tenant. To do that, I created a new VA cluster for that network and connected directly with PROD AD app.
Can I use the same VA cluster in ISC PROD tenant? I am just thinking how would I do that if I create a new VA cluster in PROD, it will generate a new va-config file.
@arshdeep_thapar You cannot use the same Virtual Appliance (VA) in two different IdentityNow tenants. Each Virtual Appliance can only be configured to connect to a single IdentityNow tenant.
To connect to multiple tenants, you would need to deploy a separate Virtual Appliance for each tenant.
While a single VA cannot connect to multiple tenants, you can deploy multiple VAs, each configured for a single tenant, to achieve connectivity to all your required IdentityNow environments.
May i know why you need to connect to same VA? As @anneragh said you cannot user same VA for different environments. If you have any other technical challenges let me know we try to give you solution.
We have a similar configuration (no ADs available for lower env). To overcome this, we connect the sources directly to our Sandbox VA and once we confirm the setup is in good standing we promote the source settings to Prod using the Configuration Hub (making sure we update the names for the IQS server, cluster and other environment variables that may differ between tenants).
We still have to configure the infra bits for IQS and VAs in the prod cluster, and sometimes we had to deal with some typos introduced during that final step, but the Configuration Hub has helped us to shave a lot of time replicating the setup required in the Admin UI.