Chat now with support
Chat with 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

PingOne

The PingOne connector allows you to connect PingOne 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 PingOne.

PingOne is a hybrid Identity-as-a-Service (IDaaS) based product that allows users to use single sign-on across different applications.

Supervisor configuration parameters

To configure the connector, following parameters are required:

  • Connector name

  • Client Id

  • API Key

  • Target URL (based on the region)

Supported objects and operations

Users
Table 283: Supported operations for Users
Operation VERB
Create User POST
Get User GET
Get Users GET
Update User PUT
Delete User DELETE
Groups
Table 284: Supported operations for Groups

Operation

VERB

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

Mandatory fields

Users
  • email[].value

  • userName

Groups

displayName

User and Group mapping

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

Table 285: User mapping
SCIM Parameter PingOne 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

email.value

email.value

email.type

email.type

email.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

password

password

profileUrl

profileUrl

title

title

userType

userType

preferredLanguage

preferredLanguage

locale

locale

timeZone

timeZone

active

active

entitlements.value

entitlements.value

roles.value

roles.value

ims.value

ims.value

ims.type

ims.type

groups.value

groups.value

groups.display

groups.display

x509Certificates.value

x509Certificates.value

extension.accountId

extension.accountId

extension.directoryId

extension.directoryId

extension.state

extension.state

extension.passwordExpired

extension.passwordExpired

meta.created

meta.created

meta.lastModified

meta.lastModified

Groups
Table 286: Group mapping
SCIM parameter PingOne parameter
id id
displayName displayName

members.value

members.value

members.display

members.display

members.type

members.type

extension.accountId

extension.accountId

extension.directoryId

extension.directoryId

meta.created

meta.created

meta.lastModified

meta.lastModified

Connector limitations

  • PingOne supports addresses of type home, work, and other. Similarly, it supports phone numbers of types work, mobile, home, fax, pager, and other. However the connector supports only one type of address and phone number.
    The connector first looks for type work. If type work is not found, the connector looks for type home.
    Else, it looks for the address and phone number of any type. If type value is not present, then the connector assigns the value of work to type.

Supervisor configuration parameters

The PingOne connector allows you to connect PingOne 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 PingOne.

PingOne is a hybrid Identity-as-a-Service (IDaaS) based product that allows users to use single sign-on across different applications.

To configure the connector, following parameters are required:

  • Connector name

  • Client Id

  • API Key

  • Target URL (based on the region)

Supported objects and operations

Users
Table 283: Supported operations for Users
Operation VERB
Create User POST
Get User GET
Get Users GET
Update User PUT
Delete User DELETE
Groups
Table 284: Supported operations for Groups

Operation

VERB

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

Mandatory fields

Users
  • email[].value

  • userName

Groups

displayName

User and Group mapping

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

Table 285: User mapping
SCIM Parameter PingOne 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

email.value

email.value

email.type

email.type

email.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

password

password

profileUrl

profileUrl

title

title

userType

userType

preferredLanguage

preferredLanguage

locale

locale

timeZone

timeZone

active

active

entitlements.value

entitlements.value

roles.value

roles.value

ims.value

ims.value

ims.type

ims.type

groups.value

groups.value

groups.display

groups.display

x509Certificates.value

x509Certificates.value

extension.accountId

extension.accountId

extension.directoryId

extension.directoryId

extension.state

extension.state

extension.passwordExpired

extension.passwordExpired

meta.created

meta.created

meta.lastModified

meta.lastModified

Groups
Table 286: Group mapping
SCIM parameter PingOne parameter
id id
displayName displayName

members.value

members.value

members.display

members.display

members.type

members.type

extension.accountId

extension.accountId

extension.directoryId

extension.directoryId

meta.created

meta.created

meta.lastModified

meta.lastModified

Connector limitations

  • PingOne supports addresses of type home, work, and other. Similarly, it supports phone numbers of types work, mobile, home, fax, pager, and other. However the connector supports only one type of address and phone number.
    The connector first looks for type work. If type work is not found, the connector looks for type home.
    Else, it looks for the address and phone number of any type. If type value is not present, then the connector assigns the value of work to type.

Supported objects and operations

The PingOne connector allows you to connect PingOne 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 PingOne.

PingOne is a hybrid Identity-as-a-Service (IDaaS) based product that allows users to use single sign-on across different applications.

Supervisor configuration parameters

To configure the connector, following parameters are required:

  • Connector name

  • Client Id

  • API Key

  • Target URL (based on the region)

Users
Table 283: Supported operations for Users
Operation VERB
Create User POST
Get User GET
Get Users GET
Update User PUT
Delete User DELETE
Groups
Table 284: Supported operations for Groups

Operation

VERB

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

Mandatory fields

Users
  • email[].value

  • userName

Groups

displayName

User and Group mapping

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

Table 285: User mapping
SCIM Parameter PingOne 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

email.value

email.value

email.type

email.type

email.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

password

password

profileUrl

profileUrl

title

title

userType

userType

preferredLanguage

preferredLanguage

locale

locale

timeZone

timeZone

active

active

entitlements.value

entitlements.value

roles.value

roles.value

ims.value

ims.value

ims.type

ims.type

groups.value

groups.value

groups.display

groups.display

x509Certificates.value

x509Certificates.value

extension.accountId

extension.accountId

extension.directoryId

extension.directoryId

extension.state

extension.state

extension.passwordExpired

extension.passwordExpired

meta.created

meta.created

meta.lastModified

meta.lastModified

Groups
Table 286: Group mapping
SCIM parameter PingOne parameter
id id
displayName displayName

members.value

members.value

members.display

members.display

members.type

members.type

extension.accountId

extension.accountId

extension.directoryId

extension.directoryId

meta.created

meta.created

meta.lastModified

meta.lastModified

Connector limitations

  • PingOne supports addresses of type home, work, and other. Similarly, it supports phone numbers of types work, mobile, home, fax, pager, and other. However the connector supports only one type of address and phone number.
    The connector first looks for type work. If type work is not found, the connector looks for type home.
    Else, it looks for the address and phone number of any type. If type value is not present, then the connector assigns the value of work to type.

Mandatory fields

The PingOne connector allows you to connect PingOne 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 PingOne.

PingOne is a hybrid Identity-as-a-Service (IDaaS) based product that allows users to use single sign-on across different applications.

Supervisor configuration parameters

To configure the connector, following parameters are required:

  • Connector name

  • Client Id

  • API Key

  • Target URL (based on the region)

Supported objects and operations

Users
Table 283: Supported operations for Users
Operation VERB
Create User POST
Get User GET
Get Users GET
Update User PUT
Delete User DELETE
Groups
Table 284: Supported operations for Groups

Operation

VERB

Create Group POST
Get Group GET
Get Groups GET
Update Group PUT
Delete Group DELETE
Users
  • email[].value

  • userName

Groups

displayName

User and Group mapping

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

Table 285: User mapping
SCIM Parameter PingOne 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

email.value

email.value

email.type

email.type

email.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

password

password

profileUrl

profileUrl

title

title

userType

userType

preferredLanguage

preferredLanguage

locale

locale

timeZone

timeZone

active

active

entitlements.value

entitlements.value

roles.value

roles.value

ims.value

ims.value

ims.type

ims.type

groups.value

groups.value

groups.display

groups.display

x509Certificates.value

x509Certificates.value

extension.accountId

extension.accountId

extension.directoryId

extension.directoryId

extension.state

extension.state

extension.passwordExpired

extension.passwordExpired

meta.created

meta.created

meta.lastModified

meta.lastModified

Groups
Table 286: Group mapping
SCIM parameter PingOne parameter
id id
displayName displayName

members.value

members.value

members.display

members.display

members.type

members.type

extension.accountId

extension.accountId

extension.directoryId

extension.directoryId

meta.created

meta.created

meta.lastModified

meta.lastModified

Connector limitations

  • PingOne supports addresses of type home, work, and other. Similarly, it supports phone numbers of types work, mobile, home, fax, pager, and other. However the connector supports only one type of address and phone number.
    The connector first looks for type work. If type work is not found, the connector looks for type home.
    Else, it looks for the address and phone number of any type. If type value is not present, then the connector assigns the value of work to type.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating