How to match Api.AppId and Api.AppKey when multiple SecureAuth appliances are not using FileSync

    Applies to:
  • Legacy SecureAuth IdP
Deployment model:
  • On Premises
  • SecureAuth IdP Version Affected:  All


    Description: When using the SecureAuth API to provide authentication, it may be necessary to match the Application ID and Application Key when there are two or more appliances present that are not already leveraging the SecureAuth FileSync tool.


    Resolution: This task can be accomplished by editing the web.config files of the realm that will be API-enabled on all appliances.


    1. Enable the API and 'Generate Credentials' on one of the SecureAuth appliances:


    2. Click on the 'System Info' tab and scroll to the bottom of the page - click on the link for the 'Web Config Editor':

    3.  Search the web.config file for the keys 'Api.AppId' and 'Api.AppKey' - you should find sections similar to those shown below:


    4. Copy these two sections into a Notepad and replace the two keys 'Api.AppId' and 'Api.AppKey' in the web.config file for the equivalent realm on the other appliances.  Once the keys have been replaced, you should see that the 'API' tab now shows the same Application ID and Application Key as was originally generated:


    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.

    0 out of 0 found this helpful



    Please sign in to leave a comment.