Chatee ahora con Soporte
Chat con el soporte

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

User and Group mapping

Egnyte lets users store files on either a company’s existing data center infrastructure or in the cloud. It can be integrated with the cloud, storage, devices, and business applications to let you control data with your current hardware.

Supervisor configuration parameters

To configure the connector, following parameters are required:

  • Connector name

  • Client_Id (API Key provided for the application)

  • Username

  • Password

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

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

To get the Client_id

  1. Login to the Egnyte cloud application.

  2. Register an application under My API Keys menu. Registered Application will have an API key that can be used as Client_Id.

Supported objects and operations

Users

Table 142: 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 143: Supported operations for Groups

Operation

VERB
Create POST
Update

PUT

Delete DELETE
Get all groups GET

Get all groups with pagination

GET

Mandatory fields

Users

  • userName

  • emails.value

  • name.givenName

  • name.familyName

  • EnterpriseExtension.authType

  • userType

  • active

Groups

  • displayName

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

Table 144: User mapping
SCIM parameter Egnyte parameter
Id Id
externalId externalId

userName

 userName

Name.FamilyName

 name.FamilyName
Name.givenName name.givenName
Name.Formatted name.Formatted
DisplayName name.Formatted
email.value email
Active active
userType userType
EnterpriseExtension.authType authType

Groups.DisplayName

groups.DisplayName

Groups.Value

groups.Value

Created

createdDate

LastModified

lastModificationDate

 

Table 145: Group mapping
SCIM parameter Egnyte parameter
Id id
displayName displayName
members.value members.value
members.display members.display

Connector limitations

  • The Role object type is not supported by cloud application for trial account. Hence, the connector does not support the role endpoint.

Connector limitations

Egnyte lets users store files on either a company’s existing data center infrastructure or in the cloud. It can be integrated with the cloud, storage, devices, and business applications to let you control data with your current hardware.

Supervisor configuration parameters

To configure the connector, following parameters are required:

  • Connector name

  • Client_Id (API Key provided for the application)

  • Username

  • Password

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

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

To get the Client_id

  1. Login to the Egnyte cloud application.

  2. Register an application under My API Keys menu. Registered Application will have an API key that can be used as Client_Id.

Supported objects and operations

Users

Table 142: 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 143: Supported operations for Groups

Operation

VERB
Create POST
Update

PUT

Delete DELETE
Get all groups GET

Get all groups with pagination

GET

Mandatory fields

Users

  • userName

  • emails.value

  • name.givenName

  • name.familyName

  • EnterpriseExtension.authType

  • userType

  • active

Groups

  • displayName

User and Group mapping

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

Table 144: User mapping
SCIM parameter Egnyte parameter
Id Id
externalId externalId

userName

 userName

Name.FamilyName

 name.FamilyName
Name.givenName name.givenName
Name.Formatted name.Formatted
DisplayName name.Formatted
email.value email
Active active
userType userType
EnterpriseExtension.authType authType

Groups.DisplayName

groups.DisplayName

Groups.Value

groups.Value

Created

createdDate

LastModified

lastModificationDate

 

Table 145: Group mapping
SCIM parameter Egnyte parameter
Id id
displayName displayName
members.value members.value
members.display members.display
  • The Role object type is not supported by cloud application for trial account. Hence, the connector does not support the role endpoint.

SugarCRM

SugarCRM is a customer relationship management (CRM) system. It allows users to manage sales-force automation, marketing campaigns, customer support, collaboration, mobile CRM, social CRM, and reporting.

Supervisor configuration parameters

To configure the connector, following parameters are required:

Supported objects and operations

Users

Table 146: Supported operations for Users

Operation

VERB

Create

POST

Update

PUT

Delete

DELETE

Get user by Id

GET

Get all users

GET

Groups

Table 147: Supported operations for Groups

Operation

VERB
Create POST
Update

PUT

Delete DELETE
Get all groups GET

Get all groups by Id

GET

Mandatory fields

Users

  • UserName

Groups

  • Not Applicable

User and Group mapping

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

Table 148: User mapping
SCIM parameter SugarCRM parameter
Id id
UserName user_name

Title

 title

PreferredLanguage

 preferred_language

name.FirstName

 first_name
name.LastName last_name
name.Formatted full_name
Address.StreetAddress address_street
Address.Region address_city
Address.Country address_country
Address.PostalCode address_postalcode
Emails.value email[0].email_address

Active

 status.Value == "Active"

Groups[].display

 team_name[].name

Groups[].value

 team_name[].id

PhoneNumbers[].Value

 phone_home

PhoneNumbers[].Value

 phone_mobile

PhoneNumbers[].Value

phone_work

Meta.Created

date_entered

Meta.LastModified

date_modified

 

Table 149: Group mapping
SCIM parameter SugarCRM parameter
id id
displayName name
Meta.created date_entered
Meta.lastModified date_modified

Connector limitations

  • Creation of a duplicate user returns the following status code:

    • 403:Forbidden
  • A CRUD operation on Users and Groups can be performed only by users with Admin credentials.
  • Multiple groups can be created with same name.

  • Group memberships cannot be added, retrieved, or modified using API calls.

  • Cloud application allows creation of a group without the Name being specified.

Supervisor configuration parameters

SugarCRM is a customer relationship management (CRM) system. It allows users to manage sales-force automation, marketing campaigns, customer support, collaboration, mobile CRM, social CRM, and reporting.

To configure the connector, following parameters are required:

Supported objects and operations

Users

Table 146: Supported operations for Users

Operation

VERB

Create

POST

Update

PUT

Delete

DELETE

Get user by Id

GET

Get all users

GET

Groups

Table 147: Supported operations for Groups

Operation

VERB
Create POST
Update

PUT

Delete DELETE
Get all groups GET

Get all groups by Id

GET

Mandatory fields

Users

  • UserName

Groups

  • Not Applicable

User and Group mapping

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

Table 148: User mapping
SCIM parameter SugarCRM parameter
Id id
UserName user_name

Title

 title

PreferredLanguage

 preferred_language

name.FirstName

 first_name
name.LastName last_name
name.Formatted full_name
Address.StreetAddress address_street
Address.Region address_city
Address.Country address_country
Address.PostalCode address_postalcode
Emails.value email[0].email_address

Active

 status.Value == "Active"

Groups[].display

 team_name[].name

Groups[].value

 team_name[].id

PhoneNumbers[].Value

 phone_home

PhoneNumbers[].Value

 phone_mobile

PhoneNumbers[].Value

phone_work

Meta.Created

date_entered

Meta.LastModified

date_modified

 

Table 149: Group mapping
SCIM parameter SugarCRM parameter
id id
displayName name
Meta.created date_entered
Meta.lastModified date_modified

Connector limitations

  • Creation of a duplicate user returns the following status code:

    • 403:Forbidden
  • A CRUD operation on Users and Groups can be performed only by users with Admin credentials.
  • Multiple groups can be created with same name.

  • Group memberships cannot be added, retrieved, or modified using API calls.

  • Cloud application allows creation of a group without the Name being specified.

Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación