Datastores not saving in New Experience

    Applies to:
  • SecureAuth Identity Platform
Deployment model:
  • Hybrid
  • Version Affected:  19.07.01+


    When multiple appliances have had their Appliance Type changed in Cloud Reports to unique names, an error occurs when attempting to save a datastore in the New Experience.


    Upon reviewing the nlog containing today's date in D:\Secureauth\ApplicationApi, you will see the following error:


    2021-02-18 14:12:33.9239|ERROR|IdP.Application.API.Controllers.ErrorController|[Error] Error at /v1/data_stores. Exception: IdP.Application.BLL.Exceptions.CloudCallException: Unprocessable Entity



    Duplicate datastore names cannot exist. If there are two Appliance Types named Dev-1 and Dev-2 and SecureAuth-AD exists in Dev-1, you cannot save a datastore with the same name in Dev-2.



    Ensure the datastore is not being saved with the same name across multiple appliances.



    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.