Troubleshooting: Failed to Save an Application with AxiosError 500 (Client Certificate Issue)

Version Affected: 20.06 onwards
 
 

Overview

When creating or updating an Application in the New Experience, the operation fails with the error Failed to save Application, AxiosError: Request failed with status code 500.

Cause

This is a generic 500 error. It is caused by a problem with the Client Certificate that the Identity Provider (IdP) uses to authenticate to its own API site (D:\SecureAuth\API), not by an actual problem with the SecureAuth0 web.config -- even though the error logged in the Api log blames the SecureAuth0 configuration.

Resolution:

To resolve this:

1. Check the Api log (for example, D:\Secureauth\Api\Log) for the full error message.
2. Decrypt the API web.config (D:\SecureAuth\Api\Web.config) and check the value of the WCFClientCertSN app setting.
3. Confirm all of the following:
   • The setting contains a certificate serial number.
   • The certificate that serial number represents is present in the Local Computer certificate store.
   • The Application Pool Identity has permission to that certificate's private key.
4. Correct any of the above that are missing or incorrect, then retry the operation.

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.