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

NutShell

NutShell is a customer relationship management (CRM) service. It can be integrated with other SaaS services for small businesses, including Google Apps.

Supervisor configuration parameters

To configure the connector, following parameters are required:

Supported objects and operations

Users

Table 134: Supported operations for Users

Operation

VERB

Create

POST

Update

PUT

Delete

DELETE

Get user by Id

GET

Get all users

GET

Get all users with pagination

GET

Groups

Table 135: Supported operations for Groups

Operation

VERB

Create POST
Update

PUT

Delete DELETE
Get group by Id GET
Get all groups GET

Get all groups with pagination

GET

Mandatory fields

Users

  • emails.value

Groups

  • displayName

User and Group mapping

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

Table 136: User mapping
SCIM parameter NutShell parameter
id id
userName email

name.familyName

lastName
name.givenName firstName
displayName name
emails[0].value email
active isEnabled
groups teams
meta.created createdTime
meta.lastModified modifiedTime

 

Table 137: Group mapping
SCIM parameter NutShell parameter
id id
displayName name
enterpriseExtension.division division
meta.created createdTime

meta.lastModified

modifiedTime

Connector limitations

  • Error messages and status codes are not customized. The following status codes are returned:

    • 200
    • 201
    • 204
    • 400
    • 401
    • 404
  • Members cannot be added or retrieved from teams (groups) via the team endpoints. This can be achieved using the user endpoints and, updating the individual users. However, considering the large number of users in live production environments, membership management is not supported by the connector, as performance issues may arise.
  • The delete operation is soft delete. Hence, it is possible to delete, or retrieve the deleted user or group multiple number of times. However, a deleted group will not be retrieved as part of the list groups response.
  • Multiple email addresses can be associated to a user. Hence, the first email Id from the Nutshell user response is considered as the email id for the SCIM user.
  • The NutShell API does not provide information on retrieval of all resources through paginated requests. Hence, the connector provides a nextCursor value, when the total resource count is divisible by requested count.

Supervisor configuration parameters

NutShell is a customer relationship management (CRM) service. It can be integrated with other SaaS services for small businesses, including Google Apps.

To configure the connector, following parameters are required:

Supported objects and operations

Users

Table 134: Supported operations for Users

Operation

VERB

Create

POST

Update

PUT

Delete

DELETE

Get user by Id

GET

Get all users

GET

Get all users with pagination

GET

Groups

Table 135: Supported operations for Groups

Operation

VERB

Create POST
Update

PUT

Delete DELETE
Get group by Id GET
Get all groups GET

Get all groups with pagination

GET

Mandatory fields

Users

  • emails.value

Groups

  • displayName

User and Group mapping

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

Table 136: User mapping
SCIM parameter NutShell parameter
id id
userName email

name.familyName

lastName
name.givenName firstName
displayName name
emails[0].value email
active isEnabled
groups teams
meta.created createdTime
meta.lastModified modifiedTime

 

Table 137: Group mapping
SCIM parameter NutShell parameter
id id
displayName name
enterpriseExtension.division division
meta.created createdTime

meta.lastModified

modifiedTime

Connector limitations

  • Error messages and status codes are not customized. The following status codes are returned:

    • 200
    • 201
    • 204
    • 400
    • 401
    • 404
  • Members cannot be added or retrieved from teams (groups) via the team endpoints. This can be achieved using the user endpoints and, updating the individual users. However, considering the large number of users in live production environments, membership management is not supported by the connector, as performance issues may arise.
  • The delete operation is soft delete. Hence, it is possible to delete, or retrieve the deleted user or group multiple number of times. However, a deleted group will not be retrieved as part of the list groups response.
  • Multiple email addresses can be associated to a user. Hence, the first email Id from the Nutshell user response is considered as the email id for the SCIM user.
  • The NutShell API does not provide information on retrieval of all resources through paginated requests. Hence, the connector provides a nextCursor value, when the total resource count is divisible by requested count.

Supported objects and operations

NutShell is a customer relationship management (CRM) service. It can be integrated with other SaaS services for small businesses, including Google Apps.

Supervisor configuration parameters

To configure the connector, following parameters are required:

Users

Table 134: Supported operations for Users

Operation

VERB

Create

POST

Update

PUT

Delete

DELETE

Get user by Id

GET

Get all users

GET

Get all users with pagination

GET

Groups

Table 135: Supported operations for Groups

Operation

VERB

Create POST
Update

PUT

Delete DELETE
Get group by Id GET
Get all groups GET

Get all groups with pagination

GET

Mandatory fields

Users

  • emails.value

Groups

  • displayName

User and Group mapping

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

Table 136: User mapping
SCIM parameter NutShell parameter
id id
userName email

name.familyName

lastName
name.givenName firstName
displayName name
emails[0].value email
active isEnabled
groups teams
meta.created createdTime
meta.lastModified modifiedTime

 

Table 137: Group mapping
SCIM parameter NutShell parameter
id id
displayName name
enterpriseExtension.division division
meta.created createdTime

meta.lastModified

modifiedTime

Connector limitations

  • Error messages and status codes are not customized. The following status codes are returned:

    • 200
    • 201
    • 204
    • 400
    • 401
    • 404
  • Members cannot be added or retrieved from teams (groups) via the team endpoints. This can be achieved using the user endpoints and, updating the individual users. However, considering the large number of users in live production environments, membership management is not supported by the connector, as performance issues may arise.
  • The delete operation is soft delete. Hence, it is possible to delete, or retrieve the deleted user or group multiple number of times. However, a deleted group will not be retrieved as part of the list groups response.
  • Multiple email addresses can be associated to a user. Hence, the first email Id from the Nutshell user response is considered as the email id for the SCIM user.
  • The NutShell API does not provide information on retrieval of all resources through paginated requests. Hence, the connector provides a nextCursor value, when the total resource count is divisible by requested count.

Mandatory fields

NutShell is a customer relationship management (CRM) service. It can be integrated with other SaaS services for small businesses, including Google Apps.

Supervisor configuration parameters

To configure the connector, following parameters are required:

Supported objects and operations

Users

Table 134: Supported operations for Users

Operation

VERB

Create

POST

Update

PUT

Delete

DELETE

Get user by Id

GET

Get all users

GET

Get all users with pagination

GET

Groups

Table 135: Supported operations for Groups

Operation

VERB

Create POST
Update

PUT

Delete DELETE
Get group by Id GET
Get all groups GET

Get all groups with pagination

GET

Users

  • emails.value

Groups

  • displayName

User and Group mapping

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

Table 136: User mapping
SCIM parameter NutShell parameter
id id
userName email

name.familyName

lastName
name.givenName firstName
displayName name
emails[0].value email
active isEnabled
groups teams
meta.created createdTime
meta.lastModified modifiedTime

 

Table 137: Group mapping
SCIM parameter NutShell parameter
id id
displayName name
enterpriseExtension.division division
meta.created createdTime

meta.lastModified

modifiedTime

Connector limitations

  • Error messages and status codes are not customized. The following status codes are returned:

    • 200
    • 201
    • 204
    • 400
    • 401
    • 404
  • Members cannot be added or retrieved from teams (groups) via the team endpoints. This can be achieved using the user endpoints and, updating the individual users. However, considering the large number of users in live production environments, membership management is not supported by the connector, as performance issues may arise.
  • The delete operation is soft delete. Hence, it is possible to delete, or retrieve the deleted user or group multiple number of times. However, a deleted group will not be retrieved as part of the list groups response.
  • Multiple email addresses can be associated to a user. Hence, the first email Id from the Nutshell user response is considered as the email id for the SCIM user.
  • The NutShell API does not provide information on retrieval of all resources through paginated requests. Hence, the connector provides a nextCursor value, when the total resource count is divisible by requested count.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating