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

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

Connector limitations

SAP Cloud Platform is an open Platform as a Service (PaaS) that offers users in-memory capabilities, core platform services, and business services for cloud applications.

Supervisor configuration parameters

To configure the connector, following parameters are required:

Supported objects and operations

Users

Table 19: Supported operations for Users

Operation

VERB

Create

POST

Update (Id)

PUT

Delete (Id)

DELETE

Get (Id)

GET

Get

GET

Pagination GET

Groups

Table 20: Supported operations for Groups

Operation

VERB

Create

POST

Update (Id)

PUT

Delete  (Id)

DELETE

Get (Id)

GET

Get

GET

Mandatory fields

Users

  • Email
  • Username

Groups

  • Group Name
  • Display Name

User and Group mapping

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

Table 21: User mapping
SCIM parameter SAP Cloud Platform parameter
Id id
UserName userName
Name.GivenName givenName
Name.FamilyName familyName

Name.HonorificPrefix

name.honorificPrefix

DisplayName displayName
Emails.Value email.value
Addresses.StreetAddress addresses.streetAddress
Addresses.Locality addresses.locality
Addresses.Region addresses.region

Addresses.PostalCode

addresses.postalCode

Addresses.Country

addresses.country

Addresses.Type

addresses.type

PhoneNumbers.value

phoneNumbers.value

UserType

userType

Locale

locale

Timezone

timeZone

Active

active

Groups.value

group.$ref

Groups.display

group.display

Extension.Organization

extension.organization

Extension.Division

extension.division

Extension.Department

extension.department

Extension.Manager.Value

extension.manager.value

Extension.Manager.DisplayName

extension.manager.displayName

Extension.ContactPreferenceTelephone

contactPreferenceTelephone

Extension.IndustryCrm

industryCrm

Extension.PasswordStatus

passwordStatus

Extension.MailVerified

mailVerified

Extension.CompanyRelationship

companyRelationship

Extension.ContactPreferenceEmail

contactPreferenceEmail

Extension.SourceSystem

sourceSystem

Extension.CostCenter

extension.costCenter

Extension.EmployeeNumber

extension.employeeNumber

Extension.CorporateGroups

corporateGroups.value

Extension.customAttributes.name

attributes.name

Extension.customAttributes.value

attributes.value

Meta.Created

meta.created

Meta.LastModified

meta.lastModified

 

Table 22: Group mapping
SCIM parameter SAP Cloud Platform parameter
id name
DisplayName displayName
Members.value members.value
Members.display members.display
Extension.GroupName extension.name
Extension.Description extension.description
  • A performance impact is expected, with a list response of Groups because each record is retrieved and counted, since SCP Groups APIs do not provide totalResults.

  • ServiceProviderAuthority contains only Id field with the same value as the tenant id of the SCP instance, as there are no APIs that can fetch the tenant details in SCP.

  • Get All Groups and Get particular group with ID operations do not retrieve Created and Last Modified fields for Groups object types.

JIRA Server

JIRA Server is an issue-tracking product used for project management, generating project reports, and bug tracking.

Supervisor configuration parameters

To configure the connector, following parameters are required:

  • Connector name

  • Username

  • Password
  • SCIM URL

Supported objects and operations

Users

Table 23: Supported operations for Users

Operation

VERB

Remove/Provision

POST

Update (Id)

PUT

Delete (Id)

DELETE

Get (Id)

GET

Get All Users

GET

Pagination

GET

Groups

Table 24: Supported operations for Groups

Operation

VERB

Create POST
Update (Id)

PUT

Delete (Id) DELETE
Get (Id) GET
Get All Groups GET

Get Groups (Id)

GET

Roles

Table 25: Supported operations for Roles

Operation

VERB

Get All Roles

GET

Get Role (Id)

GET

Mandatory fields

Users

  • User name
  • Display name
  • Email ID

Groups

  • Group Name

User and Group mapping

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

Table 26: User mapping
SCIM parameter JIRA Server parameter
Id name
UserName name

password

password

Name.Formatted displayName
DisplayName displayName
Emails.Value emailAddress
Locale locale
Timezone timeZone
Active active

Groups.value

group.name

Groups.display

group.name

 

Table 27: Group mapping
SCIM parameter JIRA Server parameter
Id name
DisplayName name
Members.value user.name
Members.display user.displayName

Connector limitations

  • The following dates are not available in User and Group resources.
    • created
    • lastModified
  • Pagination is not supported for Groups.

  • Update Group can only be used for membership management.

  • Since the application does not support id, the URL encoded user name or group name is assigned as id for the resource.

  • Leading slash (/) in clientRequest, in the RequestWrapper is restricted in REST Client (Eg: Postman) testing.

  • Invalid host name in target URL returns error 500.

  • 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

JIRA Server is an issue-tracking product used for project management, generating project reports, and bug tracking.

To configure the connector, following parameters are required:

  • Connector name

  • Username

  • Password
  • SCIM URL

Supported objects and operations

Users

Table 23: Supported operations for Users

Operation

VERB

Remove/Provision

POST

Update (Id)

PUT

Delete (Id)

DELETE

Get (Id)

GET

Get All Users

GET

Pagination

GET

Groups

Table 24: Supported operations for Groups

Operation

VERB

Create POST
Update (Id)

PUT

Delete (Id) DELETE
Get (Id) GET
Get All Groups GET

Get Groups (Id)

GET

Roles

Table 25: Supported operations for Roles

Operation

VERB

Get All Roles

GET

Get Role (Id)

GET

Mandatory fields

Users

  • User name
  • Display name
  • Email ID

Groups

  • Group Name

User and Group mapping

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

Table 26: User mapping
SCIM parameter JIRA Server parameter
Id name
UserName name

password

password

Name.Formatted displayName
DisplayName displayName
Emails.Value emailAddress
Locale locale
Timezone timeZone
Active active

Groups.value

group.name

Groups.display

group.name

 

Table 27: Group mapping
SCIM parameter JIRA Server parameter
Id name
DisplayName name
Members.value user.name
Members.display user.displayName

Connector limitations

  • The following dates are not available in User and Group resources.
    • created
    • lastModified
  • Pagination is not supported for Groups.

  • Update Group can only be used for membership management.

  • Since the application does not support id, the URL encoded user name or group name is assigned as id for the resource.

  • Leading slash (/) in clientRequest, in the RequestWrapper is restricted in REST Client (Eg: Postman) testing.

  • Invalid host name in target URL returns error 500.

  • 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

JIRA Server is an issue-tracking product used for project management, generating project reports, and bug tracking.

Supervisor configuration parameters

To configure the connector, following parameters are required:

  • Connector name

  • Username

  • Password
  • SCIM URL

Users

Table 23: Supported operations for Users

Operation

VERB

Remove/Provision

POST

Update (Id)

PUT

Delete (Id)

DELETE

Get (Id)

GET

Get All Users

GET

Pagination

GET

Groups

Table 24: Supported operations for Groups

Operation

VERB

Create POST
Update (Id)

PUT

Delete (Id) DELETE
Get (Id) GET
Get All Groups GET

Get Groups (Id)

GET

Roles

Table 25: Supported operations for Roles

Operation

VERB

Get All Roles

GET

Get Role (Id)

GET

Mandatory fields

Users

  • User name
  • Display name
  • Email ID

Groups

  • Group Name

User and Group mapping

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

Table 26: User mapping
SCIM parameter JIRA Server parameter
Id name
UserName name

password

password

Name.Formatted displayName
DisplayName displayName
Emails.Value emailAddress
Locale locale
Timezone timeZone
Active active

Groups.value

group.name

Groups.display

group.name

 

Table 27: Group mapping
SCIM parameter JIRA Server parameter
Id name
DisplayName name
Members.value user.name
Members.display user.displayName

Connector limitations

  • The following dates are not available in User and Group resources.
    • created
    • lastModified
  • Pagination is not supported for Groups.

  • Update Group can only be used for membership management.

  • Since the application does not support id, the URL encoded user name or group name is assigned as id for the resource.

  • Leading slash (/) in clientRequest, in the RequestWrapper is restricted in REST Client (Eg: Postman) testing.

  • Invalid host name in target URL returns error 500.

  • 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
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택