Converse agora com nosso suporte
Chat com o suporte

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


ChipSoft contributes to greater patient safety and more efficiency by develops cutting-edge software for healthcare professionals.

Offering fully integrated EMR/EHR solution for both individual organisations as well as organisations operating within the entire chain of care, ChipSoft is the market leader in Netherlands and in expansion across Europe.

Supervisor Configuration Parameters

  • Connector name

  • Target URL

Supported objects and operations


Table 403: Supported operations for Users



Create User


Get User by Id GET
List Users GET

Update user


Login Groups

Table 404: Supported operations for Login Groups



Get Login Group by Id


List users


User Groups

Table 405: Supported operations for User Groups



Get User Group by Id


List User Groups


Mandatory Fields

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


  • ldap
  • userName
  • displayName
  • active
  • startDate
  • endDate


The mappings are listed in the tables below.

Table 406: ChipSoft to SCIM user mapping
ChipSoft properties (Dutch and English) SCIM properties
Ldap ldap
Ldapdomain ldapDomain
Gebruikersnaam id or userName
Gebruikersomschrijving displayName
Geblokkeerd active
Startdate startDate
Enddate endDate
Afdeling department
Functie position
Soort kind
Uzinr uzinNo
Rolecode roles { value = RoleCode display = RoleCode type = blankValue }
Bedrijf company
Email emails { value = emailValue, primary = 'true, type = 'work' }
Laatsteinlogdatum lastLoginDate
Laatsteinlogtijdstip lastLoginTime
Login Groups
Inloggroepcode value
Inloggroepzoekcode searchCode
User Group
Groepcode value
Zoekcode searchCode
Table 407: ChipSoft to SCIM user group mapping
ChipSoft properties (Dutch and English) SCIM Properties
groepcode id
zoekcode searchCode
groepomschrijving displayName
soortcode typeCode
soortomschrijving speciesDescription
Table 408: ChipSoft to SCIM login group mapping
ChipSoft properties (Dutch and English) SCIM Properties
inloggroepcode id
inloggroepzoekcode searchCode
inloggroepomschrijving displayName
inloggroepactief active

Connector limitations

Due to target behavior, following has been observed:

  • User Groups and Login Groups result don’t support pagination.

  • Memberships are not managed under Groups. Instead Groups are managed under Users.

  • For any junk value in cursor, it fetches records from target. It returns last login date as "0001-01-01T00:00:00Z" and time "12:00:00" for some of the records.

  • Email is not available for any user, target also does not accept new user with email.

  • Delete is not available for any user.

  • Some of the fields are not created during create user request.

  • System throws an error when it is trying to create an existing user. It displays the value of “ldap“ in error description instead of “userName“.

  • userName (Gebruikersnaam) fields only accept 8 characters. Any string more than 8 characters will be truncated and only first 8 characters are saved.

PingOne Platform

PingOne is a cloud-based identity as a service (IDaaS) framework for secure identity access management that uses an organization based model to define tenant accounts and their related entities within the PingOne platform.

Supervisor configuration parameters

To configure the connector, following parameters are required:

Supported objects and operations


Table 409: Supported operations for Users
Operation VERB
Create User POST
Get User by Id GET
List Users GET
Update User PUT
Delete User DELETE


Table 410: Supported operations for Groups
Create Group POST
Get Group GET
Get Groups GET
Update Group PUT


Table 411: Supported operations for Populations
Get Populations by Id GET
List Populations GET

Mandatory fields


  • userName
  • population



User mapping

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

Table 412: User mapping
SCIM Parameter PingOne Parameter
id id
userName username
name.givenName name.given
name.middleName name.middle
name.formatted name.formatted
name.honorificSuffix name.honorificSuffix
name.honorificPrefix name.honorificPrefix
title title
displayName name.given
emails[].value email
active enabled
locale locale
preferredLanguage preferredLanguage
timezone timezone
groups[].value memberOfGroupIDs
externalId externalId
userType type
nickName nickname
photos[].value photo.href
addresses[].streetAddress address.streetAddress
addresses[].region address.region
addresses[].locality address.locality
addresses[].postalCode address.postalCode
phoneNumbers[].value primaryPhone
phoneNumbers[].Value mobilePhone
enterpriseExtension.accountId accountId
enterpriseExtension.identityProvider identityProvider.type
enterpriseExtension.mfaEnabled mfaEnabled
createdAt meta.created
updatedAt meta.lastModified


Table 413: Group mapping
SCIM parameter PingOne parameter
id id
displayName name
members[].value members[].id
externalId externalId
enterpriseExtension.description description
enterpriseExtension.checkSum checkSum
enterpriseExtension.customData.securityGroup customData.securityGroup
enterpriseExtension.customData.groupOwner customData.groupOwner
meta.lastModified updatedAt
meta.created createdAt

Population mapping

Table 414: Population mapping
SCIM Parameter PingOne Parameter
id id
displayName name













Connector SCIM configuration

The PingOne Platform connector is enhanced to support the configuration of SCIM connector with custom attributes and disabling of attributes. 'Users' resources in PingOne Platform connector have the support for configuring custom attributes and disabling of attributes.


  • In connector schema, datatype corresponding to multivalued custom attribute is of type string and JSON only.
  • Connector output format for multivalued custom attributes will be as shown below:

    "MultivaluedAttributeName" : "[abcd;; efgh;; xyzw;; uvty]"

  • As per the connector output format, the values will be double semicolon separated(;;) and will be enclosed inside opening and closing square brackets.
  • Opening and closing square brackets helps to ensure that the attribute is of multivalued type.

Connector limitations

  • In pagination, records are returned in multiples of 100 only due to target behaviour.
  • Custom attributes and disabling attributes are only supported in users due to target behaviour.
  • Custom attributes are supported for string and JSON attributes due to target behaviour.
  • While updating a group that was created at the population level, it should contain the same population id in the update body that was given while creating the group, while groups created at the environment level should not contain the population attribute in the update body due to target behaviour, else the target will throw the error message.

Azure DevOps

Azure DevOps is methodology that supports cohesiveness between development and operations into a smooth sailing event allowing organizations to create and improve products at a faster pace than they can with traditional software development approaches.

Supervisor configuration parameters

To configure the connector, following parameters are required.

Supported objects and operations


Table 415: Supported operations for Users



Create User


Get User by Id


List Users


Update User


Delete User


Mandatory fields

This section lists the mandatory field required to CREATE a user.


  • userName

Attributes Mappings

Different mappings associated with this connector are listed in the tables below.

Table 416: User mapping
SCIM User Azure DevOps Parameter
id id
userName user.principalName
displayName user.displayName
emails[].value user.mailAddress
enterpriseExtension.accessLevel.licensingSource accessLevel.licensingSource
enterpriseExtension.accessLevel.accountLicenseType accessLevel.accountLicenseType
enterpriseExtension.accessLevel.msdnLicenseType accessLevel.msdnLicenseType
enterpriseExtension.accessLevel.licenseDisplayName accessLevel.licenseDisplayName
enterpriseExtension.accessLevel.status accessLevel.status
enterpriseExtension.accessLevel.statusMessage accessLevel.statusMessage
enterpriseExtension.accessLevel.assignmentSource accessLevel.assignmentSource
enterpriseExtension.originId user.originId
enterpriseExtension.origin user.origin
enterpriseExtension.descriptor user.descriptor
enterpriseExtension.subjectKind user.subjectKind
enterpriseExtension.metaType user.metaType
enterpriseExtension.domain user.domain
enterpriseExtension.directoryAlias user.directoryAlias
enterpriseExtension.projectEntitlements[].assignmentSource projectEntitlements[].assignmentSource
enterpriseExtension.projectEntitlements[].isProjectPermissionInherited projectEntitlements[].projectPermissionInherited
enterpriseExtension.projectEntitlements[].projectRefId projectEntitlements[]
enterpriseExtension.projectEntitlements[].projectRefName projectEntitlements[]
enterpriseExtension.projectEntitlements[].projectGroupType projectEntitlements[].group.groupType
enterpriseExtension.projectEntitlements[].projectGroupDisplayName projectEntitlements[].group.displayName
enterpriseExtension.groupAssignments[].groupId groupAssignments[].id
enterpriseExtension.groupAssignments[].groupDescription groupAssignments[].group.description
enterpriseExtension.groupAssignments[].groupDescriptor groupAssignments[].group.descriptor
enterpriseExtension.groupAssignments[].groupDisplayName groupAssignments[].group.displayName
enterpriseExtension.groupAssignments[].groupDomain groupAssignments[].group.domain
enterpriseExtension.groupAssignments[].groupMailAddress groupAssignments[].group.mailAddress
enterpriseExtension.groupAssignments[].groupOrigin groupAssignments[].group.origin
enterpriseExtension.groupAssignments[].groupOriginId groupAssignments[].group.originId
enterpriseExtension.groupAssignments[].groupPrincipalName groupAssignments[].group.principalName
enterpriseExtension.groupAssignments[].groupSubjectkind groupAssignments[].group.subjectKind
enterpriseExtension.groupAssignments[].status groupAssignments[].status
enterpriseExtension.groupAssignments[].groupLicensingSource groupAssignments[].licenseRule.licensingSource
enterpriseExtension.groupAssignments[].groupAccountLicenseType groupAssignments[].licenseRule.accountLicenseType
enterpriseExtension.groupAssignments[].groupMsdnLicenseType groupAssignments[].licenseRule.msdnLicenseType
enterpriseExtension.groupAssignments[].groupLicenseDisplayName groupAssignments[].licenseRule.licenseDisplayName
enterpriseExtension.groupAssignments[].groupLicensingRuleStatus groupAssignments[].licenseRule.status
enterpriseExtension.groupAssignments[].groupLicensingRuleStatusMessage groupAssignments[].licenseRule.statusMessage
enterpriseExtension.groupAssignments[].groupLicensingRuleAssignmentSource groupAssignments[].licenseRuleAssignmentSource
meta.created dateCreated

Connector limitations

  • The userName should be in the format of the email address (The email address of the user that we want to add to the organization).

  • If we use the username that is already existing, the system will not throw a conflict error; instead, it will update that user or return the existing data.

  • Extensions[] are not mapped because the data is not returning from the target in response.

  • If we add a user that already exists in the organisation but is deleted, that user will have the same user ID as it had previously.

  • Only one email for a user is supported by target system.

  • Azure DevOps Target System does not return important meta information lastModified for users.

  • During the update, one attribute that is writeable should be passed.

  • Projects added through groups in users are not updatable.

Appendix: Creating a service account in Google Workspace

You must obtain a JSON file with Private Key to authorize the APIs to access data on Google Workspace domain. Create and enable the service account to obtain the private key (JSON file).

To create a project and enable the API

  1. Login to Google Cloud Platform.

  2. Click on the drop-down list next to the Google Cloud Platform label and select an organization.

    The Select a Project window is displayed.

  3. Click New Project.

    The New Project page is displayed.

  4. Enter the specific details in the relevant text field.

  5. Click Create.
  6. Click on the drop-down list next to the Google Cloud Platform label and select the project you created.

  7. Click APIs & Services tab.

  8. Click Library tab.
  9. Search for the phrase Admin SDK in the search bar and select Admin SDK from the results.

    The API Library page is displayed.

  10. Click Enable to enable the API.

To create a service account

  1. Click APIs & Services tab.

  2. Click Credentials.
  3. On the Credentials tab, click Manage Service Accounts available at the bottom right corner.

    The Service Accounts window is displayed.


    Create service account window is displayed.

  5. Enter the name of the service account in Service account name text field.

  6. Select Owner as the Role from the drop-down menu.
  7. Select the service JSON as an account Key type.

    IMPORTANT: A JSON file is required to generate an access token and it is downloaded automatically after selecting the above option.

  8. Click Create.

To select and authorize the API scopes

  1. Login to the Google workspace admin console with your domain.

  2. On the Admin console home page, click Security.

  3. Click Advanced settings.

  4. Click Managed API client access.

  5. Enter the client name and the description in the Name and Description text field respectively.

  6. Enter the email in the Email text field.

  7. Add the preferred API scopes that you want to use.

    For example, API scopes can be







    For more information on API scopes, see

  8. After adding the API scoes, click Authorize.

    The unique Id and the scopes added is displayed.

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação