Chat now with support
Chat with Support

Starling Connect Hosted - Troubleshooting Guide

About this Guide

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.

Starling Connect errors

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:

Error 400

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

  • Bad Request when an invalid attribute name is returned in the response

The procedures to verify the above mentioned scenarios are detailed below.

Bad request when mandatory fields are missing

To verify that Starling endpoints are working

  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. Correct the request body by adding or modifying the required fields and then, reinitiate.

  6. Ensure that the core schema included in the request wrapper is accurate.

  7. Apply the changes that were performed in steps 5 and 6, and send the request from One Identity Manager.

  8. Check for the success of synchronization.

Bad request when custom mapping is missing

To verify that Starling endpoints are working

  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 error description.

  5. Identify the mapping that is missing.

  6. Based on requirement of the connector, add or update a custom mapping in One Identity Manager.

  7. Reinitiate the request from One Identity Manager

  8. Check for the success of synchronization.

Bad request when there is an invalid input

To verify that Starling endpoints are working

  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 error description.

  5. Based on the error description, identify the root cause.

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

Bad request when custom attribute is missing

To verify that Starling endpoints are working

  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 error description.

  5. Identify the attribute that is missing.

  6. Based on the invalid attribute that is mentioned in the error, log in to Starling Connect and disable the attribute. Save the connector in Starling Connect.
  7. Update the schema and re-initiate the request from One Identity Manager.

  8. Check for the success of synchronization.

 

The following table consists of error messages that are returned, if different request wrapper properties are missing.

Table 1: Error messages

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)

Error 401 Unauthorized

Different error scenarios associated with Error 401 Unauthorized are listed below:

  • Invalid cloud application credentials
  • Invalid Starling credentials
  • Expired Starling Subscription
  • Deleted Starling Connector connection

The procedures to rectify the error scenarios are detailed below.

Invalid cloud application credentials

To rectify the error

  1. Log in to the cloud application and validate your credentials.

  2. Log in to the Starling account.
  3. Navigate to My Connectors.
  4. Select the required connector.
  5. Edit and update the connection parameters with accurate details.

  6. Click Save.

Invalid Starling credentials

To rectify the error

  1. Log in to the Starling account.
  2. Navigate to My Connectors.
  3. Select the required connector.
  4. Use the Starling endpoints and credentials.

Expired Starling subscription

To rectify the error

  1. Log in to the Starling account.
  2. Navigate to My Connectors.
  3. If the account is expired, get it activated.
  4. Use the Starling endpoints and credentials.

Deleted Starling Connector connection

To rectify the error

  1. Log in to the Starling account.
  2. Navigate to My Connectors.
  3. Ensure that the relevant connector is available.
Self Service Tools
Knowledge Base
Notifications & Alerts
Product Support
Software Downloads
Technical Documentation
User Forums
Video Tutorials
RSS Feed
Contact Us
Licensing Assistance
Technical Support
View All
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating