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 Retrieving Tableau Personal Access Token (PAT)

Connector limitations

The Hive connector allows you to connect Hive with One Identity Starling enabling you to take advantage of the features and products available with Starling Connect that complement and enhance Hive's services as a collaborative tool used for project planning.

Supervisor configuration parameters

To configure the connector, following parameters are required:

  • Connector name

  • Workspace Id

  • API Key

  • User Id

  • Target URL (Cloud application's instance URL used as target URI in payload)

Supported objects and operations

Users

Table 326: Supported operations for Users

Operation

VERB

Create User POST
Update User PUT
Get User by id GET
Get All Users GET

Groups

Table 327: Supported operations for Groups

Operation

VERB

GET Group by Id

GET

Get All Groups GET

Mandatory fields

Users

  • email

Groups

  • Create Group is not supported by the target system.

User and Group mapping

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

Table 328: User mapping
SCIM Parameter Hive parameter
Id id
UserName email
Name.GivenName profile.firstname
Name.FamilyName profile.lastname
Name.Formatted fullname
DisplayName fullname
Emails[0].value email

Groups

Table 329: Groups mapping
SCIM parameter Hive parameter
Id id
DisplayName name
Members.value members[]
  • Connector gets All the Groups and filters the group from the list for GET Group By Id operation since the target system does not have an API to support Get Group by Id.

  • Update User operation supports only to update GivenName and FamilyName due to target system limitation.

  • Connector does not support the meta information created and lastModified as these are not supported by the target system.

PagerDuty

PagerDuty is an incident response platform solution for IT departments. It is the leading market based product of a SaaS specialized organization that allows its customers to have an effective real-time operations platform ensuring lesser downtime and fewer outages. It is generally used for incident response, on-call management, analytics and event intelligence .

The PagerDuty connector allows you to connect PagerDutywith One Identity Starling enabling you to take advantage of the features and products available with Starling Connect that complement and enhance PagerDuty's real-time operations platfrom services.

Supervisor configuration parameters

To configure the connector, following parameters are required:

  • Connector name

  • API Key

  • Target URL (https://api.pagerduty.com)

Supported objects and operations

Users

Table 330: Supported operations for Users

Operation

VERB

Create User POST
Get a user GET
Get All Users GET
Update a user PUT
Delete a user DELETE

Groups

Table 331: Supported operations for Groups

Operation

VERB

Create a group POST
Delete a group DELETE
Get a group GET
Get all groups GET
Update a group PUT

Mandatory fields

Users

  • email.value

  • name.displayName

Groups

  • displayName

User and Group mapping

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

Table 332: User mapping
PagerDuty parameter SCIM Parameter
id id
summary extension.summary
html_url profileUrl
name displayName
email emails[].value
time_zone timezone
role roles[].value
avatar_url photos[].value
description extension.description
job_title title
teams[].id groups[].value

Groups

Table 333: Groups mapping
PagerDuty parameter SCIM parameter
id id
summary extension.summary
name displayName
description extension.description

parent[].type

extension.parent[].type

parent[].id

extension.parent[].id

groupMembersResponse.user.id

members[].value

groupMembersResponse.user.type

members[].type

Connector limitations

  • PagerDuty Target System does not return important meta information like created and lastModified.

Supervisor configuration parameters

PagerDuty is an incident response platform solution for IT departments. It is the leading market based product of a SaaS specialized organization that allows its customers to have an effective real-time operations platform ensuring lesser downtime and fewer outages. It is generally used for incident response, on-call management, analytics and event intelligence .

The PagerDuty connector allows you to connect PagerDutywith One Identity Starling enabling you to take advantage of the features and products available with Starling Connect that complement and enhance PagerDuty's real-time operations platfrom services.

To configure the connector, following parameters are required:

  • Connector name

  • API Key

  • Target URL (https://api.pagerduty.com)

Supported objects and operations

Users

Table 330: Supported operations for Users

Operation

VERB

Create User POST
Get a user GET
Get All Users GET
Update a user PUT
Delete a user DELETE

Groups

Table 331: Supported operations for Groups

Operation

VERB

Create a group POST
Delete a group DELETE
Get a group GET
Get all groups GET
Update a group PUT

Mandatory fields

Users

  • email.value

  • name.displayName

Groups

  • displayName

User and Group mapping

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

Table 332: User mapping
PagerDuty parameter SCIM Parameter
id id
summary extension.summary
html_url profileUrl
name displayName
email emails[].value
time_zone timezone
role roles[].value
avatar_url photos[].value
description extension.description
job_title title
teams[].id groups[].value

Groups

Table 333: Groups mapping
PagerDuty parameter SCIM parameter
id id
summary extension.summary
name displayName
description extension.description

parent[].type

extension.parent[].type

parent[].id

extension.parent[].id

groupMembersResponse.user.id

members[].value

groupMembersResponse.user.type

members[].type

Connector limitations

  • PagerDuty Target System does not return important meta information like created and lastModified.

Supported objects and operations

PagerDuty is an incident response platform solution for IT departments. It is the leading market based product of a SaaS specialized organization that allows its customers to have an effective real-time operations platform ensuring lesser downtime and fewer outages. It is generally used for incident response, on-call management, analytics and event intelligence .

The PagerDuty connector allows you to connect PagerDutywith One Identity Starling enabling you to take advantage of the features and products available with Starling Connect that complement and enhance PagerDuty's real-time operations platfrom services.

Supervisor configuration parameters

To configure the connector, following parameters are required:

  • Connector name

  • API Key

  • Target URL (https://api.pagerduty.com)

Users

Table 330: Supported operations for Users

Operation

VERB

Create User POST
Get a user GET
Get All Users GET
Update a user PUT
Delete a user DELETE

Groups

Table 331: Supported operations for Groups

Operation

VERB

Create a group POST
Delete a group DELETE
Get a group GET
Get all groups GET
Update a group PUT

Mandatory fields

Users

  • email.value

  • name.displayName

Groups

  • displayName

User and Group mapping

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

Table 332: User mapping
PagerDuty parameter SCIM Parameter
id id
summary extension.summary
html_url profileUrl
name displayName
email emails[].value
time_zone timezone
role roles[].value
avatar_url photos[].value
description extension.description
job_title title
teams[].id groups[].value

Groups

Table 333: Groups mapping
PagerDuty parameter SCIM parameter
id id
summary extension.summary
name displayName
description extension.description

parent[].type

extension.parent[].type

parent[].id

extension.parent[].id

groupMembersResponse.user.id

members[].value

groupMembersResponse.user.type

members[].type

Connector limitations

  • PagerDuty Target System does not return important meta information like created and lastModified.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating