Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Starling Connect Hosted - One Identity Manager Administration Guide

About this guide One Identity Starling Connect overview One Identity Starling Supported cloud applications Working with connectors Connector versions Salesforce Facebook Workplace SAP Cloud Platform JIRA Server RSA Archer SuccessFactors AWS IAM ServiceNow Dropbox Crowd Atlassian JIRA Confluence Trello Box Pipedrive SuccessFactors HR NutShell Insightly Egnyte SugarCRM Oracle IDCS Statuspage Zendesk Sell Workbooks DocuSign Citrix ShareFile Zendesk Azure AD Google Workspace Concur Tableau GoToMeeting Coupa AWS Cognito Okta DataDog Hideez Opsgenie Informatica Cloud Services AppDynamics Marketo Workday HR OneLogin PingOne Aha! SAP Litmos HackerRank Slack ActiveCampaign Webex Apigee Databricks Hive PagerDuty Dayforce Smartsheet Pingboard SAP Cloud for Customer Azure Infrastructure Oracle Fusion Cloud Majesco LuccaHR OpenText JFrog Artifactory xMatters Discourse Testrail ChipSoft PingOne Platform Azure DevOps UKG PRO Atlassian Cloud Appendix: Creating a service account in Google Workspace Appendix: Setting a trial account on Salesforce Registering the application, providing necessary permissions, retrieving Client Id and Client Secret from the Azure AD tenant Generating a private key for service account in GoToMeeting Configuring AWS IAM connector to support entitlements for User and Group Configuring Box connector to support additional email IDs for users One Identity Manager E2E integration needs for Hideez connector Configuring custom attributes for ServiceNow v.1.0 Configuring custom attributes for Coupa v.1.0 Configuring custom attributes in connectors Disabling attributes Configuring a connector that uses the consent feature Synchronization and integration of Roles object type with One Identity Manager Synchronization and integration of Workspaces object type with One Identity Manager Synchronization and integration of Products object type with One Identity Manager User centric membership Creating multi-valued custom fields in One Identity Manager Synchronization and assignment of PermissionSets to Users with One Identity Manager Connectors that support password attribute in User object Connectors that do not support special characters in the object ID Creating an app for using SCIM on Slack Enterprise Grid Organization Creating a Webex integration application, providing necessary scopes, retrieving Client Id and Client Secret Retrieving the API key from Facebook Workplace Outbound IP addresses Values for customer-specific configuration parameters in Workday HR connector Initiate an OAuth connection to SuccessFactors Creating custom editable/upsertable attributes in Successfactors employee central Custom Foundation Objects in Successfactors HR connector Configuring additional datetime offset in connectors How to Create custom attribute for Users in SuccessFactors portal SAP Cloud for Customer - Steps to add custom fields at One Identity Manager attributes Creating a Service Principal for the Azure Infrastructure Connector Workday permissions needed to integrate via the Starling Connector Configuring integration application in DocuSign Creating integration Connect Client in Coupa Retrieving Azure DevOps Personal Access Token (PAT) Setup integration system and field override service in Workday Retrieving Atlassian Cloud API Key and Directory ID Retrieving Tableau Personal Access Token (PAT)

Crowd

Crowd is a single sign-on software that lets your system administrator connect multiple applications to one user login and password. Users only need one user ID and password to access any connected platform.

Supervisor configuration parameters

To configure the connector, following parameters are required:

Supported objects and operations

Users

Table 60: Supported operations for Users

Operation

VERB

Create

POST

Update

PUT

Delete

DELETE

Get All Users

GET

Get User by Id

GET

Get All Users with pagination GET

Groups

Table 61: Supported operations for Groups

Operation

VERB

Create

POST

Update

PUT

Delete

DELETE

Get All Groups

GET

Get Group by Id

GET

Get All Groups with pagination GET

Mandatory fields

Users

  • Username
  • Password

Groups

  • DisplayName

User and Group mapping

The user and group mapping is listed in the table below.

Table 62: User mapping
SCIM parameter Crowd parameter
Id name
userName name
password password
active active
givenName first-name
familyName last-name
displayName display-name
Formatted display-name
email.value email
Created createdDate
LastModified lastModified
Table 63: Group mapping
SCIM parameter Crowd parameter
Id name
GroupName name
Active active
Description description
members.value members.name

Connector limitations

  • Crowd application does not have the ID field for Users and Groups. User name is considered as the userId, and the group name is considered as groupId.

  • Crowd cloud application does not have a created date and modified date for Groups.

  • UserName and GroupName must be used as a single term as the usage is same for userId and groupId.

  • UserName cannot be updated because it is used as an Id in cloud application.

  • DisplayName of Groups cannot be updated as required by the cloud application.

  • The connector does not support special characters in the object ID. For more information, see Connectors that do not support special characters in the object ID

Supervisor configuration parameters

Crowd is a single sign-on software that lets your system administrator connect multiple applications to one user login and password. Users only need one user ID and password to access any connected platform.

To configure the connector, following parameters are required:

Supported objects and operations

Users

Table 60: Supported operations for Users

Operation

VERB

Create

POST

Update

PUT

Delete

DELETE

Get All Users

GET

Get User by Id

GET

Get All Users with pagination GET

Groups

Table 61: Supported operations for Groups

Operation

VERB

Create

POST

Update

PUT

Delete

DELETE

Get All Groups

GET

Get Group by Id

GET

Get All Groups with pagination GET

Mandatory fields

Users

  • Username
  • Password

Groups

  • DisplayName

User and Group mapping

The user and group mapping is listed in the table below.

Table 62: User mapping
SCIM parameter Crowd parameter
Id name
userName name
password password
active active
givenName first-name
familyName last-name
displayName display-name
Formatted display-name
email.value email
Created createdDate
LastModified lastModified
Table 63: Group mapping
SCIM parameter Crowd parameter
Id name
GroupName name
Active active
Description description
members.value members.name

Connector limitations

  • Crowd application does not have the ID field for Users and Groups. User name is considered as the userId, and the group name is considered as groupId.

  • Crowd cloud application does not have a created date and modified date for Groups.

  • UserName and GroupName must be used as a single term as the usage is same for userId and groupId.

  • UserName cannot be updated because it is used as an Id in cloud application.

  • DisplayName of Groups cannot be updated as required by the cloud application.

  • The connector does not support special characters in the object ID. For more information, see Connectors that do not support special characters in the object ID

Supported objects and operations

Crowd is a single sign-on software that lets your system administrator connect multiple applications to one user login and password. Users only need one user ID and password to access any connected platform.

Supervisor configuration parameters

To configure the connector, following parameters are required:

Users

Table 60: Supported operations for Users

Operation

VERB

Create

POST

Update

PUT

Delete

DELETE

Get All Users

GET

Get User by Id

GET

Get All Users with pagination GET

Groups

Table 61: Supported operations for Groups

Operation

VERB

Create

POST

Update

PUT

Delete

DELETE

Get All Groups

GET

Get Group by Id

GET

Get All Groups with pagination GET

Mandatory fields

Users

  • Username
  • Password

Groups

  • DisplayName

User and Group mapping

The user and group mapping is listed in the table below.

Table 62: User mapping
SCIM parameter Crowd parameter
Id name
userName name
password password
active active
givenName first-name
familyName last-name
displayName display-name
Formatted display-name
email.value email
Created createdDate
LastModified lastModified
Table 63: Group mapping
SCIM parameter Crowd parameter
Id name
GroupName name
Active active
Description description
members.value members.name

Connector limitations

  • Crowd application does not have the ID field for Users and Groups. User name is considered as the userId, and the group name is considered as groupId.

  • Crowd cloud application does not have a created date and modified date for Groups.

  • UserName and GroupName must be used as a single term as the usage is same for userId and groupId.

  • UserName cannot be updated because it is used as an Id in cloud application.

  • DisplayName of Groups cannot be updated as required by the cloud application.

  • The connector does not support special characters in the object ID. For more information, see Connectors that do not support special characters in the object ID

Connector limitations

Crowd is a single sign-on software that lets your system administrator connect multiple applications to one user login and password. Users only need one user ID and password to access any connected platform.

Supervisor configuration parameters

To configure the connector, following parameters are required:

Supported objects and operations

Users

Table 60: Supported operations for Users

Operation

VERB

Create

POST

Update

PUT

Delete

DELETE

Get All Users

GET

Get User by Id

GET

Get All Users with pagination GET

Groups

Table 61: Supported operations for Groups

Operation

VERB

Create

POST

Update

PUT

Delete

DELETE

Get All Groups

GET

Get Group by Id

GET

Get All Groups with pagination GET

Mandatory fields

Users

  • Username
  • Password

Groups

  • DisplayName

User and Group mapping

The user and group mapping is listed in the table below.

Table 62: User mapping
SCIM parameter Crowd parameter
Id name
userName name
password password
active active
givenName first-name
familyName last-name
displayName display-name
Formatted display-name
email.value email
Created createdDate
LastModified lastModified
Table 63: Group mapping
SCIM parameter Crowd parameter
Id name
GroupName name
Active active
Description description
members.value members.name

  • Crowd application does not have the ID field for Users and Groups. User name is considered as the userId, and the group name is considered as groupId.

  • Crowd cloud application does not have a created date and modified date for Groups.

  • UserName and GroupName must be used as a single term as the usage is same for userId and groupId.

  • UserName cannot be updated because it is used as an Id in cloud application.

  • DisplayName of Groups cannot be updated as required by the cloud application.

  • The connector does not support special characters in the object ID. For more information, see Connectors that do not support special characters in the object ID
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation