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

OpenText

OpenText provides a complete and integrated Information Management platform, allowing companies to organize, integrate and protect data and content as it flows through business processes inside and outside the organization.

Supervisor configuration parameters

To configure the connector, following parameters are required:

Supported objects and operations

Users

Table 390: Supported operations for Users

Operation

VERB

Create User

POST

Get a user

GET

Update a user

PUT

Get all Users

GET

Delete a User

DELETE

Group

Table 391: Supported operations for Groups

Operation

VERB

Create Group

POST

Get a Group

DELETE

Get all Group

GET

Update a Group

PUT

Delete a Group

DELETE

Mandatory fields

Users

  • userName

Groups

  • displayName

User and Groups mapping

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

Table 392: User mapping
SCIM User OpenText User
id id
externalId externalId
userName userName
name.givenName name.givenName
name.formatted name.formatted
name.familyName name.familyName
displayName displayName
title title
userType userType
locale locale
timezone timezone
preferredLanguage preferredLanguage
emails[].value emails[].value
emails[].type emails[].type
phoneNumbers[].value phoneNumbers[].value
phoneNumbers[].type phoneNumbers[].type
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
userExtension.employeeNumber userExtension.employeeNumber
userExtension.costCenter userExtension.costCenter
userExtension.organization userExtension.organization
userExtension.division userExtension.division
userExtension.department userExtension.department
userExtension.manager.value userExtension.manager.value
userExtension.manager.location userExtension.manager.$ref
password password
active active
meta.created meta.created
meta.lastModified meta.lastModified
Table 393: Group mapping
SCIM Group OpenText Group
id id
displayName displayName
GroupExtension.externalId externalId
GroupExtension.emails[].value emails[].value
GroupExtension.emails[].type emails[].type
members[].value members[].value
members[].type members[].type
members[].display members[].display
meta.created meta.created
meta.lastModified meta.lastModified

Connector limitations

  • Most of the attributes like phoneNumber, addresses, preferredLanguage, timezone, locale takes any junk value due to target API behavior.

JFrog Artifactory

JFrog Artifactory is the single solution for housing and managing all the artifacts, binaries, packages, files, containers, and components for use throughout your software supply chain. JFrog Artifactory serves as your central hub for DevOps, integrating with your tools and processes to improve automation, increase integrity, and incorporate best practices along the way.

Supervisor Configuration Parameters

Supported objects and operations

Users

Table 394: Supported operations for Users

Operation

VERB

Create User

POST

Get User by Id GET
List Users GET

Update user

PUT

Delete user

DELETE

Groups

Table 395: Supported operations for Groups

Operation

VERB
Create a group POST

Delete a group

DELETE

Get Group by Id

GET

List groups

GET

Update Group

PUT

Mandatory Fields

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

Users

  • userName

  • emails[].value

  • password

Groups

  • displayName

Mappings

The mappings are listed in the tables below.

Table 396: JFrog Artifactory User to SCIM user mapping
JFrog Artifactory properties SCIM properties
name id
name UserName
group groups[].value
realm extension.realm
status active
email emails[].value
Table 397: JFrog Artifactory Group to SCIM group mapping
JFrog Artifactory properties SCIM Properties
name id
name displayName
usernames[] members[]
description extension.description
realm extension.realm

Connector limitations

  • Pagination is not supported in both users and groups endpoints.
  • When list of users or groups are retrieved from connector we get limited number of attributes, so not all the attributes in get user by id is supported in get a list of users. Only id, userName, realm, meta are supported in list of users and id, displayName, meta are supported in list of groups, this is because the target system also return limited number of attributes.
  • The resources do not have the important meta informations created date and lastModified date.

xMatters

xMatters is a service reliability platform that helps DevOps, SRES, and operations teams automate workflows, ensure infrastructure and applications are always working, and rapidly deliver products at scale. Our code-free workflow builder, adaptive approach to incident management, and real-time performance analytics all support a single goal: the happiness of your customers.

Supervisor Configuration Parameters

Supported objects and operations

Users

Table 398: Supported operations for Users

Operation

VERB

Create

POST

Get User by Id GET
List Users GET

Update user

PUT

Delete user

DELETE

Groups

Table 399: Supported operations for Groups

Operation

VERB
Create group POST

Delete group

DELETE

Get Group by Id

GET

List groups

GET

Update Group

PUT

Roles

Table 400: Supported operations for Roles

Operation

VERB
Get Role By Id GET

List Roles

GET

Mandatory Fields

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

Users

  • userName

  • name.familyName

  • name.givenName

  • roles[].value

Groups

  • displayName

Mappings

The mappings are listed in the tables below.

Table 401: xMatters User to SCIM user mapping
xMatters properties SCIM properties
id id
links.self profileUrl
targetName userName
firstName name.givenName
firstName lastName name.formatted
lastName name.familyName

firstName lastName

displayName

roles[].name

roles[].display

status

active

recipentType

userType

timezone

timezone

language

preferredLanguage

whenCreated

meta.created

whenUpdated

meta.lastModified

Table 402: xMatters Group to SCIM group mapping
xMatters properties SCIM Properties
id id
targetName displayName
status extension.active
description extension.description
members[].id members[].value

createTime

meta.created

members[].targetName

members[].display

Table 403: xMatters Role to SCIM role mapping
xMatters properties SCIM Properties
id id
name role[].name

Connector limitations

  • List Groups do not support the members Attribute in query attributes.

  • Roles do not support query attribute feature.

  • If invalid Id value is used while deleting Users and Groups, the response has status code 204 due to target behavior.

Discourse

Discourse is the 100% open source discussion platform built for the next decade of the Internet. Use it as a mailing list, discussion forum, long-form chat room, and more! Discourse is a from-scratch reboot, an attempt to reimagine what a modern Internet discussion forum should be today, in a world of ubiquitous smartphones, tablets, Facebook, and Twitter.

Supervisor Configuration Parameters

  • Connector name
  • Api Key
  • Target URL (https://instance_name.discourse.group)

Supported objects and operations

Users

Table 404: Supported operations for Users

Operation

VERB

Create User

POST

Get User by Id GET
List Users GET

Update user

PUT

Delete user

DELETE

Groups

Table 405: Supported operations for Groups

Operation

VERB
Create a group POST

Delete a group

DELETE

Get Group by Id

GET

List groups

GET

Update Group

PUT

Mandatory Fields

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

Users

  • userName

  • emails[].value

  • displayName

  • password

Groups

  • displayName

Mappings

The mappings are listed in the tables below.

Table 406: Discourse User to SCIM user mapping
Discourse properties SCIM properties

id

id

username UserName
name displayName
active active
admin extension.admin
created_at meta.Created

name

name.formatted

emails

emails[].value

Table 407: Discourse Group to SCIM group mapping
Discourse properties SCIM Properties
name id
name displayName
members[].id members[].value

Connector limitations

  • Discourse Target System does not return important meta information lastModified for users and created and lastModified for groups.
  • In pagination, the records can be returned in multiples of 100 only.
  • Modifying the displayName of a group would change its id.
  • Specifying the attribute 'members' in Groups LIST will not return the members as getting the members would slow down the LIST request processing as there would be as many number of additional membership requests as the number of groups in the list response are needed due to a target API behavior.
  • StartIndex value is ignored in this connector due to the target API behavior (page based).
  • Without passing anything in update request body, the update API runs and give the old data.
  • In Users/Get user by id, target behaviour which ignores some characters from id. "1cc1" is considered as "1" itself.
  • While giving invalid API key, target gives 404 (not found) instead of 401 (unauthorized).
Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación