Version Affected: [19.07.01+]
Description:
When running SISU, the installer never completes and the following is displayed in the Debug log:
11/2/2020 2:00:46 PM - DEBUG: Calling GetResource from the following assembly: D:\SecureAuth\SecureAuth0\bin\MFC.SecureAuth.License.dll
11/2/2020 2:00:46 PM - DEBUG: Calling GetResource from the following assembly: D:\SecureAuth\SecureAuth0\bin\MFC.SecureAuth.License.dll
11/2/2020 2:00:46 PM - ERROR: Update93Components: System.Net.Http.HttpRequestException: Could not parse SecureStorage API response ---> Newtonsoft.Json.JsonReaderException: Unexpected character encountered while parsing value: <. Path '', line 0, position 0.
at Newtonsoft.Json.JsonTextReader.ParseValue()
at Newtonsoft.Json.Linq.JObject.Load(JsonReader reader, JsonLoadSettings settings)
at Newtonsoft.Json.Linq.JObject.Parse(String json, JsonLoadSettings settings)
at SA.Common.WebConfig.JsonApiClient.CreateSecureStore(String baseSecureStoreUri)
--- End of inner exception stack trace ---
at SA.Common.WebConfig.JsonApiClient.CreateSecureStore(String baseSecureStoreUri)
at SA.Common.WebConfig.WebConfigUpdater.UpdateSecureStoreApiConnections(String baseUrl)
at SecureAuthIdPSetupUtility.Configurer.UpdateAppSettings()
11/2/2020 2:00:46 PM - ERROR: error during preinstallation Could not parse SecureStorage API response
11/2/2020 2:00:46 PM - DEBUG: Exception caught during installation:Could not parse SecureStorage API response
Upon reviewing the SecureStorageApi endpoints in the IIS log, 500 status codes are being thrown.
Cause:
SISU is failing to install the necessary .NET Core components.
Resolution:
Install the .NET Core components based on the Identity Platform version, per this document:
https://docs.secureauth.com/2307/en/secureauth-compatibility-guide.html#required--net-versions
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.
Comments
Please sign in to leave a comment.