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

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 Amazon S3 AWS 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 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 Amazon S3 AWS 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 Service Principal to authenticate the Azure resource management REST APIs for Azure Infrastructure connector

Connector limitations

Oracle IDCS is a cloud-based identity management service that integrates with existing systems and directories. Users can develop, access and deploy their applications from one platform. It works with both cloud and on-premises applications.

Supervisor configuration parameters

To configure the connector, following parameters are required:

Supported objects and operations

Users

Table 146: Supported operations for Users

Operation

VERB

Create

POST

Update

PUT

Delete

DELETE

Get all users

GET

Get user by id

GET

Get users with Pagination GET

Groups

Table 147: Supported operations for Groups

Operation

VERB

Create

POST

Update

PUT

Delete 

DELETE

Get

GET

Get

GET

Mandatory fields

Users

  • userName

  • emails.value

  • name.familyName

Groups

  • displayName

User and Group mapping

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

Table 148: User mapping
SCIM Parameter Oracle IDCS parameter
Id id
userName userName
externalId externalId
name.givenName name.givenName

name.familyName

name.familyName

name.middleName name.middleName
name.formatted name.formatted
name.honorificPrefix name.honorificPrefix
name.honorificSuffix name.honorificSuffix
displayName displayName
nickName nickName
emails.value email.value
emails.type email.type
emails.primary email.primary
addresses.formatted addresses.formatted
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
phoneNumbers.type phoneNumbers.type
phoneNumbers.primary phoneNumbers.primary
password password
profileUrl profileUrl
title title
userType userType
preferredLanguage preferredLanguage
locale locale
timezone timeZone
active active
entitlements.value entitlements.value
entitlements.display entitlements.display
entitlements.type entitlements.type
roles.value roles.value
roles.display roles.display
roles.type roles.type
groups.value groups.value

groups.display

groups.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.costCenter

extension.costCenter

extension.employeeNumber

extension.employeeNumber

meta.created

meta.created

meta.lastModified

meta.lastModified

 

Table 149: Group mapping
SCIM parameter Oracle IDCS parameter
id id
displayName displayName
Members.value members.value
Members.display members.display
extension.externalId extension.externalId
extension.description extension.description

meta.created

meta.created

meta.lastModified

meta.lastModified

  • Oracle IDCS does not validate the values provided for the roles in the user request and the same is getting assigned to the user. No validation is performed for the type, value properties for the roles. Same is the case with entitlements.

  • Groups will not be returned with the create user response.

  • Sub-Groups cannot be added in Group Memberships.

Statuspage

Statuspage is a status and incident communication tool that helps service providers keep customers and employees informed during downtime. It lets users add separate components for each part of the infrastructure or functional part of service.

Supervisor configuration parameters

To configure the connector, following parameters are required:

  • Connector name

  • API key (user API key under Manage AccountAPI tab) for the cloud account

  • Organization Id (Organization Id under Manage AccountAPI tab) for the cloud account

  • Target URL of the cloud account

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

Supported objects and operations

Users

Table 150: Supported operations for Users

Operation

VERB

Create User

POST

Delete User

DELETE

Get User

GET

Get All Users

GET

Groups

Not Applicable

Mandatory fields

Users

  • emails.value

  • password

Groups

Not Applicable

User and Group mapping

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

Table 151: User mapping
SCIM parameter Statuspage parameter
Id id
UserName email
last_name name.familyName
first_name name.givenName
first_namelast_name

name.formatted

first_namelast_name displayName
email emails[0].value

created_at

meta.created

updated_at

meta.lastModified

Groups

Not Applicable

Connector limitations

  • Update operation for Users, resource type Groups and Pagination are not supported.

  • Retrieving a specific user would be relatively slow due to API limitations.

Supervisor configuration parameters

Statuspage is a status and incident communication tool that helps service providers keep customers and employees informed during downtime. It lets users add separate components for each part of the infrastructure or functional part of service.

To configure the connector, following parameters are required:

  • Connector name

  • API key (user API key under Manage AccountAPI tab) for the cloud account

  • Organization Id (Organization Id under Manage AccountAPI tab) for the cloud account

  • Target URL of the cloud account

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

Supported objects and operations

Users

Table 150: Supported operations for Users

Operation

VERB

Create User

POST

Delete User

DELETE

Get User

GET

Get All Users

GET

Groups

Not Applicable

Mandatory fields

Users

  • emails.value

  • password

Groups

Not Applicable

User and Group mapping

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

Table 151: User mapping
SCIM parameter Statuspage parameter
Id id
UserName email
last_name name.familyName
first_name name.givenName
first_namelast_name

name.formatted

first_namelast_name displayName
email emails[0].value

created_at

meta.created

updated_at

meta.lastModified

Groups

Not Applicable

Connector limitations

  • Update operation for Users, resource type Groups and Pagination are not supported.

  • Retrieving a specific user would be relatively slow due to API limitations.

Supported objects and operations

Statuspage is a status and incident communication tool that helps service providers keep customers and employees informed during downtime. It lets users add separate components for each part of the infrastructure or functional part of service.

Supervisor configuration parameters

To configure the connector, following parameters are required:

  • Connector name

  • API key (user API key under Manage AccountAPI tab) for the cloud account

  • Organization Id (Organization Id under Manage AccountAPI tab) for the cloud account

  • Target URL of the cloud account

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

Users

Table 150: Supported operations for Users

Operation

VERB

Create User

POST

Delete User

DELETE

Get User

GET

Get All Users

GET

Groups

Not Applicable

Mandatory fields

Users

  • emails.value

  • password

Groups

Not Applicable

User and Group mapping

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

Table 151: User mapping
SCIM parameter Statuspage parameter
Id id
UserName email
last_name name.familyName
first_name name.givenName
first_namelast_name

name.formatted

first_namelast_name displayName
email emails[0].value

created_at

meta.created

updated_at

meta.lastModified

Groups

Not Applicable

Connector limitations

  • Update operation for Users, resource type Groups and Pagination are not supported.

  • Retrieving a specific user would be relatively slow due to API limitations.

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택