지금 지원 담당자와 채팅
지원 담당자와 채팅

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

User and Group mapping

The Slack connector allows you to connect Slack with One Identity Starling enabling you to take advantage of the features and products available with Starling Connect that complement and enhance the services provided by Slack.

Slack is a cloud-based platform, where users can create and maintain multiple dedicated and organized spaces to allow team members to effectively communicate with each other in a seamless manner.

Connector Configuration

Slack connector requires customer consent to retrieve resource details using REST APIs. Currently, the Slack connector supports the configuration of a single tenant connector only.

NOTE:

Supervisor configuration parameters

To configure the connector, following parameters are required:

  • Connector name

  • Client Id for the app

  • Client Secret of the app

  • Target URL (Cloud application's instance URL used as target URI in payload - Example: https://api.slack.com/scim/v1/)

  • Instance DateTime Offset (refer Configuring additional datetime offset in connectors for more details).

Supported objects and operations

Users

Table 302: Supported operations for Users

Operation

VERB

Create User POST
Get User GET
Get Users GET
Update User PUT
Delete User DELETE

Groups

Table 303: Supported operations for Groups

Operation

VERB

Create Group POST
Get Group GET
Get Groups GET
Update Group PUT
Delete Group DELETE

Mandatory fields

This section lists the mandatory fields required to create a User or Group.

User

  • userName

  • emails.value

Group

  • displayName

The user and group mappings are listed in the tables below.

Table 304: User mapping
SCIM Parameter Slack parameter
id id
userName userName
name.givenName name.givenName
name.familyName name.familyName
name.honorificPrefix name.honorificPrefix
displayName displayName
nickName nickName
emails[].value emails[].value
emails[].primary emails[].primary
addresses[].streetAddress addresses[].streetAddress
addresses[].locality addresses[].locality

addresses[].region

addresses[].region

addresses[].postalCode

addresses[].postalCode

addresses[].country addresses[].country
phoneNumbers[].value phoneNumbers[].value
phoneNumbers[].type phoneNumbers[].type
phoneNumbers[].primary phoneNumbers[].primary
profileUrl profileUrl

title

title

userType

userType

password password (Write-only and never returned)
preferredLanguage preferredLanguage
locale locale
timezone timezone
active active

groups[].value

groups[].value

groups[].display

groups[].display

roles[].value

roles[].value

roles[].primary roles[].primary
photos[].value photos[].value
photos[].type photos[].type
extension.costCenter extension.costCenter
extension.department extension.department

extension.division

extension.division

extension.employeeNumber

extension.employeeNumber

extension.organization

extension.organization

extension.manager.managerId

extension.manager.value

meta.created

meta.created

Groups

Table 305: Groups mapping
SCIM parameter Slack parameter
id id
displayName displayName
members[].value members[].value
members[].display members[].display

meta.created

meta.created

Connector limitations

  • Create User operation can create only Active users in the target application. Update User operation can be used to make the user Inactive.
  • You cannot create a new user or update the name of an existing user using the name of an existing user or channel.
  • The email id provided in the user name field during the User Create operation will automatically be converted to a user name according to the target application standard.
  • There is no endpoint available for Roles and any string value can be assigned as a Role of a User. However, the number of strings that can be assigned as a Role of a User has been limited to maximum one.
  • Last Modified Date is not returned in meta of Users and Groups.
  • Target system supports only soft delete of users. Users deleted using soft delete will still be accessible to read, update and delete.
  • Error 429 occurs when the requests from a SCIM client exceed the SCIM API rate limit of the Slack target application.

  • The special characters used in userName are converted to underscore in Create User and Update User operations.

  • User Name is replaced by the Nick Name when it is passed in a Create User and Update User request.

Connector limitations

The Slack connector allows you to connect Slack with One Identity Starling enabling you to take advantage of the features and products available with Starling Connect that complement and enhance the services provided by Slack.

Slack is a cloud-based platform, where users can create and maintain multiple dedicated and organized spaces to allow team members to effectively communicate with each other in a seamless manner.

Connector Configuration

Slack connector requires customer consent to retrieve resource details using REST APIs. Currently, the Slack connector supports the configuration of a single tenant connector only.

NOTE:

Supervisor configuration parameters

To configure the connector, following parameters are required:

  • Connector name

  • Client Id for the app

  • Client Secret of the app

  • Target URL (Cloud application's instance URL used as target URI in payload - Example: https://api.slack.com/scim/v1/)

  • Instance DateTime Offset (refer Configuring additional datetime offset in connectors for more details).

Supported objects and operations

Users

Table 302: Supported operations for Users

Operation

VERB

Create User POST
Get User GET
Get Users GET
Update User PUT
Delete User DELETE

Groups

Table 303: Supported operations for Groups

Operation

VERB

Create Group POST
Get Group GET
Get Groups GET
Update Group PUT
Delete Group DELETE

Mandatory fields

This section lists the mandatory fields required to create a User or Group.

User

  • userName

  • emails.value

Group

  • displayName

User and Group mapping

The user and group mappings are listed in the tables below.

Table 304: User mapping
SCIM Parameter Slack parameter
id id
userName userName
name.givenName name.givenName
name.familyName name.familyName
name.honorificPrefix name.honorificPrefix
displayName displayName
nickName nickName
emails[].value emails[].value
emails[].primary emails[].primary
addresses[].streetAddress addresses[].streetAddress
addresses[].locality addresses[].locality

addresses[].region

addresses[].region

addresses[].postalCode

addresses[].postalCode

addresses[].country addresses[].country
phoneNumbers[].value phoneNumbers[].value
phoneNumbers[].type phoneNumbers[].type
phoneNumbers[].primary phoneNumbers[].primary
profileUrl profileUrl

title

title

userType

userType

password password (Write-only and never returned)
preferredLanguage preferredLanguage
locale locale
timezone timezone
active active

groups[].value

groups[].value

groups[].display

groups[].display

roles[].value

roles[].value

roles[].primary roles[].primary
photos[].value photos[].value
photos[].type photos[].type
extension.costCenter extension.costCenter
extension.department extension.department

extension.division

extension.division

extension.employeeNumber

extension.employeeNumber

extension.organization

extension.organization

extension.manager.managerId

extension.manager.value

meta.created

meta.created

Groups

Table 305: Groups mapping
SCIM parameter Slack parameter
id id
displayName displayName
members[].value members[].value
members[].display members[].display

meta.created

meta.created

  • Create User operation can create only Active users in the target application. Update User operation can be used to make the user Inactive.
  • You cannot create a new user or update the name of an existing user using the name of an existing user or channel.
  • The email id provided in the user name field during the User Create operation will automatically be converted to a user name according to the target application standard.
  • There is no endpoint available for Roles and any string value can be assigned as a Role of a User. However, the number of strings that can be assigned as a Role of a User has been limited to maximum one.
  • Last Modified Date is not returned in meta of Users and Groups.
  • Target system supports only soft delete of users. Users deleted using soft delete will still be accessible to read, update and delete.
  • Error 429 occurs when the requests from a SCIM client exceed the SCIM API rate limit of the Slack target application.

  • The special characters used in userName are converted to underscore in Create User and Update User operations.

  • User Name is replaced by the Nick Name when it is passed in a Create User and Update User request.

ActiveCampaign

The ActiveCampaign connector allows you to connect ActiveCampaign with One Identity Starling enabling you to take advantage of the features and products available with Starling Connect that complement and enhance ActiveCampaign’s wide range of marketing services and solutions.

Supervisor configuration parameters

To configure the connector, following parameters are required:

Supported objects and operations

Users

Table 306: Supported operations for Users

Operation

VERB

Create User

POST

Update User PUT
Delete User DELETE
Get User GET
Get All users GET

Groups

Table 307: Supported operations for Groups

Operation

VERB

Create Group POST
Update Group PUT
Get Group GET
Delete Group DELETE
Get Group Members GET
Get all Groups GET

Mandatory fields

This section lists the mandatory fields required to create Users and Groups.

Users

  • Name.GivenName

  • Name.FamilyName

  • Email

  • Username

  • password

  • GroupId

Groups

DisplayName

User and Group mapping

The user and group mappings are listed in the tables below.

Users

Table 308: User mapping
SCIM parameter ActiveCampaign parameter
Id id
UserName username
DisplayName firstName+ lastName
Name.GivenName firstName

Name.FamilyName

lastName

Emails.Value

email

Groups[].value (readOnly)

groupid

PhoneNumbers[].value

phone

Meta.Created

cdate

Meta.LastModified

udate

Password

Password

userExtension.groupId (WriteOnly)

groupid

 

Table 309: Group mapping
SCIM Parameter ActiveCampaign parameter
Id Id
displayName title
members[].value (groupMembersResponse) userid
groupExtension.Description Descript

Connector limitations

  • GroupId is a writeOnly mandatory extension property while creating or updating a User.

  • Membership operations are not implemented due to the unavailability of APIs.

  • The Groups property in the schema of the User is an on-demand attribute, which will not be fetched during the operation GET User by Id unless the request has an attribute for groups.

Supervisor configuration parameters

The ActiveCampaign connector allows you to connect ActiveCampaign with One Identity Starling enabling you to take advantage of the features and products available with Starling Connect that complement and enhance ActiveCampaign’s wide range of marketing services and solutions.

To configure the connector, following parameters are required:

Supported objects and operations

Users

Table 306: Supported operations for Users

Operation

VERB

Create User

POST

Update User PUT
Delete User DELETE
Get User GET
Get All users GET

Groups

Table 307: Supported operations for Groups

Operation

VERB

Create Group POST
Update Group PUT
Get Group GET
Delete Group DELETE
Get Group Members GET
Get all Groups GET

Mandatory fields

This section lists the mandatory fields required to create Users and Groups.

Users

  • Name.GivenName

  • Name.FamilyName

  • Email

  • Username

  • password

  • GroupId

Groups

DisplayName

User and Group mapping

The user and group mappings are listed in the tables below.

Users

Table 308: User mapping
SCIM parameter ActiveCampaign parameter
Id id
UserName username
DisplayName firstName+ lastName
Name.GivenName firstName

Name.FamilyName

lastName

Emails.Value

email

Groups[].value (readOnly)

groupid

PhoneNumbers[].value

phone

Meta.Created

cdate

Meta.LastModified

udate

Password

Password

userExtension.groupId (WriteOnly)

groupid

 

Table 309: Group mapping
SCIM Parameter ActiveCampaign parameter
Id Id
displayName title
members[].value (groupMembersResponse) userid
groupExtension.Description Descript

Connector limitations

  • GroupId is a writeOnly mandatory extension property while creating or updating a User.

  • Membership operations are not implemented due to the unavailability of APIs.

  • The Groups property in the schema of the User is an on-demand attribute, which will not be fetched during the operation GET User by Id unless the request has an attribute for groups.

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택