Starling Connect Hosted - Troubleshooting Guide

Error 403 occurs when the user does not have the required access privileges.

To rectify the error, ensure that the user has required access privileges.

The error scenario associated with Error 404 Not found occurs when the Starling endpoints are not accessible.

To ensure that Starling endpoints are working

1. Open a SCIM Client (for example, Postman).

2. Perform a GET operation for endpoints mentioned below:

   • Schemas

   • ServiceProviderConfig

   • ResourceTypes

   • Users

   • Groups

3. Verify the JSON response, to check whether it is successful.

The following error scenarios are associated with Error 406 :

• Function Host Down
• Connector West US is stopped and the East US is up and running for MRF Archer

The procedures to verify the error scenarios are detailed below:

Function Host Down

To verify the scenario, check and ensure that the Function host is up and running.

Connector West US is stopped and the East US is up and running for MRF Archer

Error 406 is displayed for a short time when the connector West US is stopped and the East US is up and running for MRF Archer.

To verify the scenario, do the following:

1. Pass a request when both the West and East US connector are up and running.
2. Verify that a successful response is displayed.
3. Stop the West US app service.
4. Pass a request and verify the response.

Error 409 Conflict occurs when duplicate values are used in unique fields of the application.

To rectify the error

1. Copy the failed request body from One Identity Manager.

2. Paste the request body at a SCIM client (for example, Postman).

3. Perform a POST/PUT operation for the request on Starling Endpoints as required.

4. Observe the JSON response with the error description.

5. Based on the error description, identify the unique fields that cause the conflict.

6. Correct the request body by adding or modifying the unique fields.