How To: Match Api.AppId and Api.AppKey Across Appliances Without FileSync

Version Affected: All

 

Overview

This article explains how to make two or more SecureAuth appliances share the same API Application ID and Application Key for a realm, when those appliances are not using SecureAuth FileSync to stay in sync. This is done by copying the values directly from one appliance’s web.config file into the equivalent realm’s web.config file on each other appliance.

1. On the realm that already has the desired Application ID and Application Key (typically the production realm), open the API tab and copy both values into a text file.
2. Copy that text file to each appliance that needs the same values.
3. On the realm to be updated, back up its web.config file (for example, D:\SecureAuth\SecureAuth<realm>\web.config), then decrypt it from the Admin Console.
4. Open web.config in a text editor and search for Api.AppId. Delete its current value and paste in the new one, keeping it inside double quotes.
5. Search for Api.AppKey and repeat the same replacement.
6. Save the file.
7. In the Admin Console, open the realm’s API tab and confirm the updated values are shown.
8. Click Save on the realm to re-encrypt web.config.
9. Click away from the API tab and back to it again, to confirm the updated values were actually saved.

Special Considerations:

If the appliances use FileSync, this article does not apply — FileSync already replicates the API key values along with the rest of the configuration, so no extra steps are needed.

This article assumes each appliance uses a separate authentication directory, or that the same certificate is already used on each realm where the values need to be synced. If the appliances instead share the same authentication directory, the licensing certificate from one IdP server must also be imported into the other and selected on its System Info tab — that certificate is what allows items pushed into the shared authentication directory to be encrypted correctly.

SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.