Starling Connect Hosted - Release Notes

Changed UI config path of 'token URL' parameter results in Bad Request error in an already configured and saved Salesforce connector in Starling.

Workaround

1. Go to the Starling portal, edit the configured / saved connector.
2. Ensure all configuration parameters are filled correctly with the recommended formats.
3. Save the connector.
4. Verify the success of the synchronization.

The initial full synchronization at One Identity Manager is unable to complete as the Dayforce APIs have rate limits in place and the error with HTTP status code 429 is returned when requesting more that 100 resources in a minute .

Workaround

Delay each request in the connector for a configured amount of time (say 500ms) to avoid the issue of rate limit.

In the Starling Connect Connectors for SalesForce connector, unable to list the users by applying filters for preferredLanguage attribute. For the results to be displayed in the TargetBrowser, use an underscore (_) instead of a hyphen (-).

In the Starling Connect Connectors for Apigee connector, Get All Users does not return the displayName as it is not available in the target system. However, Get User by ID returns the display name with the other available attributes of the User.

In the Starling Connect Connectors for Apigee connector, Create User operation fails intermittently and an Internal Server Error 500 is displayed due to the Target system API behavior.

In the Starling Connect Connectors for Apigee connector, the Get All and Create User operations may occasionally take more time to respond for requests.

In the Starling Connect Connectors for SalesForce connector, unable to list the users by applying filters for all extension attributes, complex sub-attributes, and some of the core attributes.

In the Starling Connect connector for WebEx connector, an inappropriate error message is displayed after clicking Give Consent on the General Configuration window. To resolve the issue, provide the redirect URL in the integration app of WebEx.

Starling Connect does not support special characters with the exceptions of a few such as @, +, _, - and so on in the object ID, for example, User ID and Group ID.

The connectors that have this issue are

• AmazonS3AWS
• Crowd
• JiraServer
• Apigee

In the Starling Connect connector for Azure AD connector, in the Prod EU environment, only the single tenant connector configuration is available.

In Starling Connect Connector for the Salesforce v.4.0 connector, you can disable a mandatory child attribute by disabling its parent attribute for the User object. For example, the mandatory child attribute familyName under the parent attribute name in the User object is disabled when you disable its parent attribute. This is not the recommended practice and you should not be to disable a mandatory child attribute by disabling its non-mandatory parent attribute.

In Starling Connect Connector for the SuccessFactors HR connector, if a custom attribute has the character / or \ as part of attribute navigation, you must replace these characters with $$ when you enter the custom attribute in Starling Connect.

Starling connect UI does not validate the custom attributes that are configured in the cloud application. Hence, make sure that the valid custom attributes are configured in Starling Connect UI. This is common for all connectors that allow you to configure custom attributes in Starling Connect UI.

In Starling Connect Connector for the RSA Archer connector, the GET Users endpoint returns \n in the address attribute. This is in line with the response received from the RSA Archer target system API call. Starling Connect would not remove this \n new line character in the response to avoid displaying the complete address in a single line, without line breaks, in One Identity Manager Endpoint.

In Starling Connect Connector for the Hideez connector, One Identity Manager Integration cannot use the existing synchronization templates. The endpoints provided by Hideez are different when compared to that of other Starling connectors. And, none of the existing One Identity Manager Synchronization templates that are available for SCIM Connector or CHS modules template would work with Hideez endpoints.

In Starling Connect Connector for the Hideez connector, appropriate error messages are not being displayed.

In Starling Connect Connector for Concur, after deleting the user on One Identity Manager, an error message is displayed that the request could not be completed successfully though the user is deleted in the target instance. Note this error does not affect the functionality as the user is already deleted.

In Starling Connect Connector for Facebook Workplace, removing the last member of a group deletes the group automatically.

In Starling Connect Connector for JIRA Server, deletion of a group is not allowed.

In Starling Connect Connector for RSA Archer, it is not possible to have multiple log-ins with the same instance.

In Starling Connect Connector for JIRA Server, the Get Specific Group request, that has special characters from the Supervisor returns 404 Not Found error.

When an incorrect SCIM or target URL, such as an invalid cloud instance URL is configured in the Supervisor, the error code 404 and error message Invalid cloud endpoint must be displayed. However, the expected error code and message are not displayed in all the cases. This issue is applicable to all the connectors.

In Starling Connect Connector for Dropbox, a user is not able to update optional field values to blank values.

In Starling Connect Connector for Dropbox, results are displayed to an end user, even when the startIndex value is greater than the TotalResults.

In Starling Connect Connector for RSA Archer, an error is displayed if an user is created using an incorrect locale value .

In Starling Connect Connector for Insightly, certain Group names are not displayed in the Manager console, in the 7.1.4 version of One Identity Manager.

In Starling Connect Connector for Insightly, an error is returned, in the Target system browser for Groups, in the 8.0.2 version of One Identity Manager, with HF 30426

In Starling Connect Connector for Egnyte, a successful response is received when the Get User operation is requested, when the Password field is left blank.

In Starling Connect Connector for Egnyte, creation of user fails if a special character is provided in the userName field.

In Starling Connect Connector for Egnyte, the sync fails if the number of groups is more than ten for a trial account.

In Starling Connect Connector for Atlassian JIRA Confluence, the pagination for users is truncated to the first 1000 resources, beyond which the users are not displayed.

In Starling Connect Connector for Atlassian JIRA Confluence, SCIM to UCI synchronization does not have all the user accounts as the email address is not available in the cloud user response.

In Starling Connect Connector for Coupa, the implementation of Group and Role memberships are User centric operations. This is because the Coupa target system does not provide dedicated APIs to work with Groups and Roles object types.

As a work around, the endpoint or client system has to be customized for successful integration of Groups and Roles memberships.