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)

DocuSign

DocuSign allows users to manage digital transactions for electronic documents including contracts and signatures. Its features include authentication services, user identity management, and workflow automation.

Supervisor configuration parameters

To configure the connector, following parameters are required. Refer section Configuring integration application for detailed instructions.

  • Connector name

  • Admin User Id

  • Client Id

  • Private Key

  • Auth Server (account-d.docusign.com for developer environments and account.docusign.com for production environments)

  • Account ID

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

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

Supported objects and operations

Users

Table 162: Supported operations for Users

Operation

VERB

Create User

POST

Update User

PUT

Delete User

DELETE

Get User

GET

Get All Users

GET

Get All Users with Pagination

GET

Groups

Table 163: Supported operations for Groups

Operation

VERB
Create Group POST
Update Group PUT

Delete Group

DELETE

Get Group

GET

Get All Groups

GET

Get All Groups with Pagination

GET

Update Membership

PUT

Mandatory fields

Users

  • UserName
  • Email

Groups

  • DisplayName

User and Group mapping

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

Table 164: User mapping
SCIM parameter DocuSign parameter
Id userId
UserName userName
UserType userType
DisplayName userName
Title jobTitle
name.GivenName firstName
name.FamilyName lastName

Addresses.StreetAddress

workAddress.address1

Addresses.Locality

workAddress.address2

Addresses.Region

workAddress.city

Addresses.Country

workAddress.country

Addresses.postalCode

workAddress.postalCode

PhoneNumbers.Value

workAddress.phone

Emails.Value

email

Active

userStatus

Groups

groupList

Meta.Created

createdDateTime

 

Table 165: Group mapping
SCIM parameter DocuSign parameter

id

groupId

displayName

groupName

Connector limitations

  • Username update is accepted only when no first and last name provided.

  • Add and update of Users address not supported.

  • Intermittently, you cannot update the users when the activation is in pending status.

  • Active user cannot be created. After the created user activates the account through the email link, the user is considered to be an Active user.

  • Combination of user name and email duplication will result in conflict error response.

Supervisor configuration parameters

DocuSign allows users to manage digital transactions for electronic documents including contracts and signatures. Its features include authentication services, user identity management, and workflow automation.

To configure the connector, following parameters are required. Refer section Configuring integration application for detailed instructions.

  • Connector name

  • Admin User Id

  • Client Id

  • Private Key

  • Auth Server (account-d.docusign.com for developer environments and account.docusign.com for production environments)

  • Account ID

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

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

Supported objects and operations

Users

Table 162: Supported operations for Users

Operation

VERB

Create User

POST

Update User

PUT

Delete User

DELETE

Get User

GET

Get All Users

GET

Get All Users with Pagination

GET

Groups

Table 163: Supported operations for Groups

Operation

VERB
Create Group POST
Update Group PUT

Delete Group

DELETE

Get Group

GET

Get All Groups

GET

Get All Groups with Pagination

GET

Update Membership

PUT

Mandatory fields

Users

  • UserName
  • Email

Groups

  • DisplayName

User and Group mapping

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

Table 164: User mapping
SCIM parameter DocuSign parameter
Id userId
UserName userName
UserType userType
DisplayName userName
Title jobTitle
name.GivenName firstName
name.FamilyName lastName

Addresses.StreetAddress

workAddress.address1

Addresses.Locality

workAddress.address2

Addresses.Region

workAddress.city

Addresses.Country

workAddress.country

Addresses.postalCode

workAddress.postalCode

PhoneNumbers.Value

workAddress.phone

Emails.Value

email

Active

userStatus

Groups

groupList

Meta.Created

createdDateTime

 

Table 165: Group mapping
SCIM parameter DocuSign parameter

id

groupId

displayName

groupName

Connector limitations

  • Username update is accepted only when no first and last name provided.

  • Add and update of Users address not supported.

  • Intermittently, you cannot update the users when the activation is in pending status.

  • Active user cannot be created. After the created user activates the account through the email link, the user is considered to be an Active user.

  • Combination of user name and email duplication will result in conflict error response.

Supported objects and operations

DocuSign allows users to manage digital transactions for electronic documents including contracts and signatures. Its features include authentication services, user identity management, and workflow automation.

Supervisor configuration parameters

To configure the connector, following parameters are required. Refer section Configuring integration application for detailed instructions.

  • Connector name

  • Admin User Id

  • Client Id

  • Private Key

  • Auth Server (account-d.docusign.com for developer environments and account.docusign.com for production environments)

  • Account ID

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

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

Users

Table 162: Supported operations for Users

Operation

VERB

Create User

POST

Update User

PUT

Delete User

DELETE

Get User

GET

Get All Users

GET

Get All Users with Pagination

GET

Groups

Table 163: Supported operations for Groups

Operation

VERB
Create Group POST
Update Group PUT

Delete Group

DELETE

Get Group

GET

Get All Groups

GET

Get All Groups with Pagination

GET

Update Membership

PUT

Mandatory fields

Users

  • UserName
  • Email

Groups

  • DisplayName

User and Group mapping

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

Table 164: User mapping
SCIM parameter DocuSign parameter
Id userId
UserName userName
UserType userType
DisplayName userName
Title jobTitle
name.GivenName firstName
name.FamilyName lastName

Addresses.StreetAddress

workAddress.address1

Addresses.Locality

workAddress.address2

Addresses.Region

workAddress.city

Addresses.Country

workAddress.country

Addresses.postalCode

workAddress.postalCode

PhoneNumbers.Value

workAddress.phone

Emails.Value

email

Active

userStatus

Groups

groupList

Meta.Created

createdDateTime

 

Table 165: Group mapping
SCIM parameter DocuSign parameter

id

groupId

displayName

groupName

Connector limitations

  • Username update is accepted only when no first and last name provided.

  • Add and update of Users address not supported.

  • Intermittently, you cannot update the users when the activation is in pending status.

  • Active user cannot be created. After the created user activates the account through the email link, the user is considered to be an Active user.

  • Combination of user name and email duplication will result in conflict error response.

Mandatory fields

DocuSign allows users to manage digital transactions for electronic documents including contracts and signatures. Its features include authentication services, user identity management, and workflow automation.

Supervisor configuration parameters

To configure the connector, following parameters are required. Refer section Configuring integration application for detailed instructions.

  • Connector name

  • Admin User Id

  • Client Id

  • Private Key

  • Auth Server (account-d.docusign.com for developer environments and account.docusign.com for production environments)

  • Account ID

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

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

Supported objects and operations

Users

Table 162: Supported operations for Users

Operation

VERB

Create User

POST

Update User

PUT

Delete User

DELETE

Get User

GET

Get All Users

GET

Get All Users with Pagination

GET

Groups

Table 163: Supported operations for Groups

Operation

VERB
Create Group POST
Update Group PUT

Delete Group

DELETE

Get Group

GET

Get All Groups

GET

Get All Groups with Pagination

GET

Update Membership

PUT

Users

  • UserName
  • Email

Groups

  • DisplayName

User and Group mapping

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

Table 164: User mapping
SCIM parameter DocuSign parameter
Id userId
UserName userName
UserType userType
DisplayName userName
Title jobTitle
name.GivenName firstName
name.FamilyName lastName

Addresses.StreetAddress

workAddress.address1

Addresses.Locality

workAddress.address2

Addresses.Region

workAddress.city

Addresses.Country

workAddress.country

Addresses.postalCode

workAddress.postalCode

PhoneNumbers.Value

workAddress.phone

Emails.Value

email

Active

userStatus

Groups

groupList

Meta.Created

createdDateTime

 

Table 165: Group mapping
SCIM parameter DocuSign parameter

id

groupId

displayName

groupName

Connector limitations

  • Username update is accepted only when no first and last name provided.

  • Add and update of Users address not supported.

  • Intermittently, you cannot update the users when the activation is in pending status.

  • Active user cannot be created. After the created user activates the account through the email link, the user is considered to be an Active user.

  • Combination of user name and email duplication will result in conflict error response.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating