Chat now with support
Chat mit Support

Starling Connect Hosted - Release Notes

Starling Connect

Starling Connect

Release Notes

13 February 2020

These release notes provide information about the 13 February 2020 Starling Connect release.

Topics:

About this release

These release notes provide information about the 13 February 2020 Starling Connect release.

New features

The following is a list of new features in this release of Starling Connect.
The following were the new features in the previous releases of Starling Connect.

Resolved issues

The following issues were resolved in this release of Starling Connect.

There are no resolved issues in this release.

The following issues were resolved in previous releases of Starling Connect.
Closed30 January 2020 resolved issues
Closed6 January 2020 resolved issues
Closed19 December 2019 resolved issues
Closed11 December 2019 resolved issues
 
Closed21 November 2019 resolved issues

Known issues

The following is a list of issues, including those attributed to third-party products, known to exist at the time of release.

Table 17: General known issues
Known issue Issue ID

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.

220412

In Starling Connect Connector for OpsGenie connector, assign and unassign operations for Roles is functional tested but the integration testing is partially done as this requires One Identity Manager onsite customization.

221217

In Starling Connect Connector for DataDog connector, assign and unassign operations for Roles is functional tested but the integration testing is partially done as this requires One Identity Manager onsite customization.

221216

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

220065

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.

114620

In Starling Connect Connector for SAP Cloud Platform, Password Policy must be applied appropriately in One Identity Manager to enable the User Create feature to work successfully. 51186
In Starling Connect Connector for Facebook Workplace, to use a group, the group must contain at least one member. 51185

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

51170

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

51518

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

53534

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

51276

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.

54659

In Starling Connect Connector for Amazon S3 AWS, addition or removal of entitlements for Groups is currently not supported by One Identity Manager.

79680

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

88925

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

88927

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

98585

In Starling Connect Connector for RSA Archer, when the last pagination request is sent, the next cursor comes up.

99100

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.

102317

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

102344

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.

104777

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

105413

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

105441

In Starling Connect Connector for Coupa, Groups and Roles membership operations are not supported in the current release. Support for the feature would be available in the subsequent release.

125325

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.

127066

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.

127068

 

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.

128542

When both the East US and West US App Services are not available, the 500 Internal Server Error, with the message "An Error occurred while sending the request", is displayed. This is because the Cloud application RSA Archer always returns the error message as 500 Internal Server Error. This issue is common for all connectors.

139480

Self-Service-Tools
Knowledge Base
Benachrichtigungen und Warnmeldungen
Produkt-Support
Software-Downloads
Technische Dokumentationen
Benutzerforen
Videoanleitungen
RSS Feed
Kontakt
Unterstützung bei der Lizenzierung
Technische Support
Alle anzeigen
Verwandte Dokumente