Converse agora com nosso suporte
Chat com o suporte

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 S3 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 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 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

Opsgenie

The Opsgenie connector allows you to connect Opsgenie with One Identity Starling enabling you to take advantage of the features and products available with Starling Connect that complement and enhance Opsgenie’s incident management platform that allows collaboration among the required stakeholders to stay in control during service disruptions.

Supervisor configuration parameters

To configure the connector, following parameters are required:

  • Connector name

  • API

  • Target URL (Cloud application's instance URL used as target URI in payload - Example: https://api.opsgenie.com/v2 and for EU region it will be https://api.eu.opsgenie.com/v2)

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

Supported objects and operations

Users

Table 229: Supported operations for Users

Operation

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

Groups

Table 230: Supported operations for Groups

Operation

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

Roles

Table 231: Supported operations for Roles

Operation

VERB
Get custom user role GET
Get custom user roles GET

Mandatory fields

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

Users

  • emails[].value

  • displayName

Groups

  • displayName

Mappings

The mappings are listed in the tables below.

Users

Table 232: User mapping
SCIM parameter Opsgenie parameter
id id
username userName
fullName name.formatted
fullName displayName
username emails[0].value
userAddress.line addresses[].streetAddress

userAddress.city

addresses[].locality

userAddress.state

addresses[].region

userAddress.zipCode

addresses[].postalCode

userAddress.country

addresses[].country

blocked

active

locale

locale

timeZone

timezone

role.id

roles[].value

user teams[].id

groups[].value

skypeUsername

userExtension.skypeUsername

createdAt

meta.created

Groups

Table 233: Group mapping
SCIM parameter Opsgenie parameter
id id
name displayName
members[]user.id members[].value
description extension.description
createdAt meta.created

Connector limitations

  • When you update an user, the updated emailID will not be retrieved until it is verified by the user.
  • When you create or update a Group, you can use only dots, dashes and underscores for Group names.

 

Synchronization and integration of Roles object type with One Identity Manager

For more information, see Synchronization and integration of Roles object type with One Identity Manager

Supervisor configuration parameters

The Opsgenie connector allows you to connect Opsgenie with One Identity Starling enabling you to take advantage of the features and products available with Starling Connect that complement and enhance Opsgenie’s incident management platform that allows collaboration among the required stakeholders to stay in control during service disruptions.

To configure the connector, following parameters are required:

  • Connector name

  • API

  • Target URL (Cloud application's instance URL used as target URI in payload - Example: https://api.opsgenie.com/v2 and for EU region it will be https://api.eu.opsgenie.com/v2)

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

Supported objects and operations

Users

Table 229: Supported operations for Users

Operation

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

Groups

Table 230: Supported operations for Groups

Operation

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

Roles

Table 231: Supported operations for Roles

Operation

VERB
Get custom user role GET
Get custom user roles GET

Mandatory fields

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

Users

  • emails[].value

  • displayName

Groups

  • displayName

Mappings

The mappings are listed in the tables below.

Users

Table 232: User mapping
SCIM parameter Opsgenie parameter
id id
username userName
fullName name.formatted
fullName displayName
username emails[0].value
userAddress.line addresses[].streetAddress

userAddress.city

addresses[].locality

userAddress.state

addresses[].region

userAddress.zipCode

addresses[].postalCode

userAddress.country

addresses[].country

blocked

active

locale

locale

timeZone

timezone

role.id

roles[].value

user teams[].id

groups[].value

skypeUsername

userExtension.skypeUsername

createdAt

meta.created

Groups

Table 233: Group mapping
SCIM parameter Opsgenie parameter
id id
name displayName
members[]user.id members[].value
description extension.description
createdAt meta.created

Connector limitations

  • When you update an user, the updated emailID will not be retrieved until it is verified by the user.
  • When you create or update a Group, you can use only dots, dashes and underscores for Group names.

 

Synchronization and integration of Roles object type with One Identity Manager

For more information, see Synchronization and integration of Roles object type with One Identity Manager

Supported objects and operations

The Opsgenie connector allows you to connect Opsgenie with One Identity Starling enabling you to take advantage of the features and products available with Starling Connect that complement and enhance Opsgenie’s incident management platform that allows collaboration among the required stakeholders to stay in control during service disruptions.

Supervisor configuration parameters

To configure the connector, following parameters are required:

  • Connector name

  • API

  • Target URL (Cloud application's instance URL used as target URI in payload - Example: https://api.opsgenie.com/v2 and for EU region it will be https://api.eu.opsgenie.com/v2)

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

Users

Table 229: Supported operations for Users

Operation

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

Groups

Table 230: Supported operations for Groups

Operation

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

Roles

Table 231: Supported operations for Roles

Operation

VERB
Get custom user role GET
Get custom user roles GET

Mandatory fields

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

Users

  • emails[].value

  • displayName

Groups

  • displayName

Mappings

The mappings are listed in the tables below.

Users

Table 232: User mapping
SCIM parameter Opsgenie parameter
id id
username userName
fullName name.formatted
fullName displayName
username emails[0].value
userAddress.line addresses[].streetAddress

userAddress.city

addresses[].locality

userAddress.state

addresses[].region

userAddress.zipCode

addresses[].postalCode

userAddress.country

addresses[].country

blocked

active

locale

locale

timeZone

timezone

role.id

roles[].value

user teams[].id

groups[].value

skypeUsername

userExtension.skypeUsername

createdAt

meta.created

Groups

Table 233: Group mapping
SCIM parameter Opsgenie parameter
id id
name displayName
members[]user.id members[].value
description extension.description
createdAt meta.created

Connector limitations

  • When you update an user, the updated emailID will not be retrieved until it is verified by the user.
  • When you create or update a Group, you can use only dots, dashes and underscores for Group names.

 

Synchronization and integration of Roles object type with One Identity Manager

For more information, see Synchronization and integration of Roles object type with One Identity Manager

Mandatory fields

The Opsgenie connector allows you to connect Opsgenie with One Identity Starling enabling you to take advantage of the features and products available with Starling Connect that complement and enhance Opsgenie’s incident management platform that allows collaboration among the required stakeholders to stay in control during service disruptions.

Supervisor configuration parameters

To configure the connector, following parameters are required:

  • Connector name

  • API

  • Target URL (Cloud application's instance URL used as target URI in payload - Example: https://api.opsgenie.com/v2 and for EU region it will be https://api.eu.opsgenie.com/v2)

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

Supported objects and operations

Users

Table 229: Supported operations for Users

Operation

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

Groups

Table 230: Supported operations for Groups

Operation

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

Roles

Table 231: Supported operations for Roles

Operation

VERB
Get custom user role GET
Get custom user roles GET

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

Users

  • emails[].value

  • displayName

Groups

  • displayName

Mappings

The mappings are listed in the tables below.

Users

Table 232: User mapping
SCIM parameter Opsgenie parameter
id id
username userName
fullName name.formatted
fullName displayName
username emails[0].value
userAddress.line addresses[].streetAddress

userAddress.city

addresses[].locality

userAddress.state

addresses[].region

userAddress.zipCode

addresses[].postalCode

userAddress.country

addresses[].country

blocked

active

locale

locale

timeZone

timezone

role.id

roles[].value

user teams[].id

groups[].value

skypeUsername

userExtension.skypeUsername

createdAt

meta.created

Groups

Table 233: Group mapping
SCIM parameter Opsgenie parameter
id id
name displayName
members[]user.id members[].value
description extension.description
createdAt meta.created

Connector limitations

  • When you update an user, the updated emailID will not be retrieved until it is verified by the user.
  • When you create or update a Group, you can use only dots, dashes and underscores for Group names.

 

Synchronization and integration of Roles object type with One Identity Manager

For more information, see Synchronization and integration of Roles object type with One Identity Manager

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação