This document describes common issues related to Starling Connect connectors that may occur while connecting to different cloud applications using Starling Connect. It also defines how to diagnose and troubleshoot different issues concerning Starling Connect. This document will be revised by the Support team as and when information update happens.
Different errors associated with Starling Connect are detailed in this section. This section also describes different procedures to be followed to verify the error and the scenario.
The errors related to Starling Connect are as follows:
Different error scenarios associated with Error 400 are listed below:
Bad request when mandatory fields are missing
Bad request when custom mapping is missing
Bad request when there is an invalid input
The procedures to verify the above mentioned scenarios are detailed below.
To verify that Starling Endpoints are working
Copy the failed request body from One Identity Manager.
Paste the request body at a SCIM client (for example, Postman).
Perform a POST/PUT operation for the request on Starling Endpoints as required.
Observe the JSON response with the error description.
Correct the request body by adding or modifying the required fields and then, reinitiate.
Ensure that the core schema included in the request wrapper is accurate.
Apply the changes that were performed in steps 5 and 6, and send the request from One Identity Manager.
Check for the success of synchronization.
To verify that Starling Endpoints are working
Copy the failed request body from One Identity Manager.
Paste the request body at a SCIM client (for example, Postman).
Perform a POST/PUT operation for the request on Starling Endpoints as required.
Observe the JSON response with error description.
Identify the mapping that is missing.
Based on requirement of the connector, add or update a custom mapping in One Identity Manager.
Reinitiate the request from One Identity Manager
Check for the success of synchronization.
To verify that Starling Endpoints are working
Copy the failed request body from One Identity Manager.
Paste the request body at a SCIM client (for example, Postman).
Perform a POST/PUT operation for the request on Starling Endpoints as required.
Observe the JSON response with error description.
Based on the error description, identify the root cause.
Correct the request body by adding or modifying the required fields.
The following table consists of error messages that are returned, if different request wrapper properties are missing.
|
Request Wrapper Property |
Error Message |
|---|---|
| Method | Required property missing in Request Wrapper |
| ClientRequest | Required property missing in Request Wrapper |
| Body | Required property missing in Request Body |
| targetURi | Required property missing in Request Wrapper |
| serviceCredentials | Required property missing in Request Wrapper |
| AuthenticationType | enum -0 (default) |
| ConfigProperties | Required property missing in Request Wrapper |
| credential information (username, password, clientID, and so on) | Credential information missing in Request Wrapper |
|
ConfigProperties |
Required property missing in Request Wrapper (from connector) |
Different error scenarios associated with Error 401 Unauthorized are listed below:
The procedures to rectify the error scenarios are detailed below.
To rectify the error
Log in to the cloud application and validate your credentials.
Edit and update the connection parameters with accurate details.
To rectify the error
To rectify the error
To rectify the error
© 2024 One Identity LLC. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center
