Chat now with support
Chat con el soporte

Starling Connect Identity Manager Integrated - Administration Guide

About this guide One Identity Starling Connect overview One Identity Starling Supported cloud applications Configuring connectors Connector versions Salesforce Facebook Workplace SAP Cloud Platform JIRA Server RSA Archer SuccessFactors Amazon S3 AWS 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 GSuite Concur Tableau GoToMeeting Coupa AWS Cognito Okta Creating a service account in GSuite Setting a trial account on Salesforce Working with Azure AD Generating a private key for service account in GoToMeeting OneIM limitations Configuring Amazon S3 AWS connector to support entitlements for User and Group Outbound IP addresses

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:

  • Connector name

  • Client Id

  • Client Secret
  • Username

  • Password

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

Supported objects and operations

Users
Table 112: Supported operations for Users

Operation

VERB

Create

POST

Update

PUT

Delete

DELETE

Get user by Id

GET

Get all users

GET

Groups
Table 113: 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 114: 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 115: 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.

Oracle IDCS

Oracle IDCS is a cloud-based identity management service that integrates with existing systems and directories. Users can develop, access and deploy their applications from one platform. It works with both cloud and on-premises applications.

Supervisor configuration parameters

To configure the connector, following parameters are required:

Supported objects and operations

Users
Table 116: Supported operations for Users

Operation

VERB

Create

POST

Update

PUT

Delete

DELETE

Get all users

GET

Get user by id

GET

Get users with Pagination GET
Groups
Table 117: Supported operations for Groups

Operation

VERB

Create

POST

Update

PUT

Delete 

DELETE

Get

GET

Get

GET

Mandatory fields

Users
  • userName

  • emails.value

  • name.familyName

Groups
  • displayName

User and Group mapping

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

Table 118: User mapping
SCIM Parameter Oracle IDCS parameter
Id id
userName userName
externalId externalId
name.givenName name.givenName

name.familyName

name.familyName

name.middleName name.middleName
name.formatted name.formatted
name.honorificPrefix name.honorificPrefix
name.honorificSuffix name.honorificSuffix
displayName displayName
nickName nickName
emails.value email.value
emails.type email.type
emails.primary email.primary
addresses.formatted addresses.formatted
addresses.streetAddress addresses.streetAddress
addresses.locality addresses.locality
addresses.region addresses.region
addresses.postalCode addresses.postalCode
addresses.country addresses.country
addresses.type addresses.type
phoneNumbers.value phoneNumbers.value
phoneNumbers.type phoneNumbers.type
phoneNumbers.primary phoneNumbers.primary
password password
profileUrl profileUrl
title title
userType userType
preferredLanguage preferredLanguage
locale locale
timezone timeZone
active active
entitlements.value entitlements.value
entitlements.display entitlements.display
entitlements.type entitlements.type
roles.value roles.value
roles.display roles.display
roles.type roles.type
groups.value groups.value

groups.display

groups.display

extension.organization

extension.organization

extension.division

extension.division

extension.department

extension.department

extension.manager.value

extension.manager.value

extension.manager.displayName

extension.manager.displayName

extension.costCenter

extension.costCenter

extension.employeeNumber

extension.employeeNumber

meta.created

meta.created

meta.lastModified

meta.lastModified

 

Table 119: Group mapping
SCIM parameter Oracle IDCS parameter
id id
displayName displayName
Members.value members.value
Members.display members.display
extension.externalId extension.externalId
extension.description extension.description

meta.created

meta.created

meta.lastModified

meta.lastModified

Connector limitations

  • Oracle IDCS does not validate the values provided for the roles in the user request and the same is getting assigned to the user. No validation is performed for the type, value properties for the roles. Same is the case with entitlements.

  • Groups will not be returned with the create user response.

  • Sub-Groups cannot be added in Group Memberships.

Statuspage

Statuspage is a status and incident communication tool that helps service providers keep customers and employees informed during downtime. It lets users add separate components for each part of the infrastructure or functional part of service.

Supervisor configuration parameters

To configure the connector, following parameters are required:

  • Connector name

  • API key (user API key under Manage AccountAPI tab) for the cloud account

  • Organization Id (Organization Id under Manage AccountAPI tab) for the cloud account

  • Target URL of the cloud account

Supported objects and operations

Users
Table 120: Supported operations for Users

Operation

VERB

Create User

POST

Delete User

DELETE

Get User

GET

Get All Users

GET

Groups

Not Applicable

Mandatory fields

Users
  • emails.value

  • password
Groups

Not Applicable

User and Group mapping

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

Table 121: User mapping
SCIM parameter Statuspage parameter
Id id
UserName email
last_name name.familyName
first_name name.givenName
first_namelast_name

name.formatted

first_namelast_name displayName
email emails[0].value

created_at

meta.created

updated_at

meta.lastModified

Groups

Not Applicable

Connector limitations

  • Update operation for Users, resource type Groups and Pagination are not supported.

  • Retrieving a specific user would be relatively slow due to API limitations.

Zendesk Sell

Zendesk Sell provides a web-based sales platform with tools for emailing, phone dialing, pipeline management, forecasting, and reporting.

Supervisor configuration parameters

To configure the connector, following parameters are required:

  • Connector name

  • API Key

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

Supported objects and operations

Users
Table 122: Supported operations for Users

Operation

VERB

Get User

GET

Get All Users

GET

Get All Users with Pagination

GET

Groups

Not Applicable

Mandatory fields

Users

Not Applicable

Groups

Not Applicable

User and Group mapping

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

Table 123: User mapping
SCIM parameter Zendesk Sell parameter
Id id
userName email
name.Formatted name

DisplayName

name

email.value

email

PhoneNumbers.value

phone_number

Active status
Timezone timeZone

Groups.Value

group.id

Groups.display

group.name

Extension.manager.value

reports_to

Created

created_at

LastModified

updated_at

Groups

Not Applicable

Connector limitations

  • Create, Update, and Delete users are not supported by Zendesk Sell connector.

  • The resultant (User) objects count of pagination is always in the multiples of 100, unless cloud has less than 100 records in a page.

Documentos relacionados