Bug: 500 Error Opening Datastore Summary/Properties After Upgrading to 24.4.7

Version Affected: 24.4.7
Bug Number: EE-3901
Bug Status: Open - No Permanent Fix
Fixed in Version(s): Not yet fixed as of this article's last review — check current release notes for status.

 

Overview

After upgrading to SecureAuth Identity Platform 24.4.7, opening the Summary or Properties page for one or more Datastores throws a 500 error, visible in the browser's developer tools, caused by an exception in the MaskCredentials() function.

 

Cause

The Admin API log shows an exception similar to the following:

Error|SecureAuth.Admin.API.WebApiConfig|[Log] GET|https://localhost/api/v3/data_stores/ac123b45-67c8-9101-1213-1415cf5be83e|System.NullReferenceException: Object reference not set to an instance of an object.
   at SecureAuth.Integration.Broker.Models.DataStoreConfigBase.MaskCredentials()

This is thrown by the MaskCredentials() function, which expects the Datastore to have a value saved in its Service Account credentials/password field. If the affected Datastore has no value saved there at all, MaskCredentials() has nothing to mask and throws a null reference exception instead.

 

Resolution / Workaround

Use one of the following workarounds:

1. On an IdP appliance still running an earlier version, open the affected Datastore's Summary page and enter Service Account credentials or a password — even invalid credentials satisfy the check — then save.
2. If that is not possible, delete the Datastore and recreate it.

If you cannot access an earlier version and cannot delete the Datastore, contact SecureAuth Support for assistance.


 

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.