지금 지원 담당자와 채팅
지원 담당자와 채팅

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 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 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 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 Service Principal to authenticate the Azure resource management REST APIs for Azure Infrastructure connector

One Identity Manager E2E integration needs for Hideez connector

One Identity Manager Integration cannot use the existing synchronization templates for Hideez connector. The endpoints provided by Hideez are different when compared to that of other Starling connectors. And, none of the existing One Identity Manager Synchronization templates that are available for SCIM Connector or for CHS modules template would work with Hideez endpoints.

Here is more explanation about the same:

  • The regular SCIM Synchronization and One Identity Starling Connect Synchronization template cannot be used while the synchronization project is created, since the endpoints do not match.
  • The One Identity Starling Connect HR template also cannot be used because Hideez does not have the costcenter and location endpoints. It is mandatory for a connector to have the costcenter and location endpoints if you want to use the One Identity Starling Connect HR template.
  • The recommended approach would to create a blank project template and then map the endpoints manually.

Configuring custom attributes for ServiceNow v.1.0

This feature allows you to configure custom attributes in Starling Connector during connector subscription. You can provide the list of custom attributes in a defined format with the name, type and allowed values of the attributes. The custom mappings in the One Identity Manager provide the values for these custom attributes.

NOTE: While configuring ServiceNow v.1.0 connector, if you do not want to configure any custom attributes, then enter the value None in the Custom Properties field.

To configure custom attributes in ServiceNow v.1.0:

  1. Create a Custom Attribute in ServiceNow.

    NOTE:The Starling Platform currently supports only the types String, dateTime, True/False and Choice in the ServiceNow sys_user table.

  2. To configure the custom attributes in Starling UI, enter the Custom Properties in the specified format in the Starling Platform.

  3. On the One Identity Manager, map the created custom attributes that were specified in the Starling Platform.

  4. Perform a synchronization and verify if the custom attributes are available in the One Identity Manager.

    NOTE:

    • The Starling UI for registering a ServiceNow connector has an input field to provide the custom attributes to be mapped in the connector's User resource type apart from the default mapped attributes.

    • The custom attributes in the User resource type must be in the following format:

      {field_name}|{data_type}|{choice_value1,choice_value2,etc};{field_name}|{data_type}|{choice_value1,choice_value2,etc};etc.

      Example:

      u_employee_status|string;u_date_of_termination_of_employments|DateTime;u_test_field_with_canonical_values|string|Choice 1,Choice 2,Choice 3

      field_name = Column name in ServiceNow

      data_type = string (or) boolean (or) datetime

    • All custom attributes are mapped in the enterprise user extensions.

    • The supported data types in the Starling Connect ServiceNow connector are string, boolean and dataTime.

      Choice type in the ServiceNow will become string type in OneIM with Canonical Values.

    • Only simple json attributes are supported. Complex json attributes are not supported.

    • All custom user attributes have 'mutability': 'readWrite', 'returned': 'default', 'caseExact': 'false', 'required': 'false', 'multiValued': 'false','uniqueness': 'none'.

Configuring custom attributes for Coupa v.1.0

This feature allows you to configure custom attributes in Starling Connector during connector subscription. You can provide the list of custom attributes in a defined format with the name, type and allowed values of the attributes. The custom mappings in the One Identity Manager provide the values for these custom attributes.

NOTE:

  • Only String and Boolean data types are supported currently by Coupa connector.
  • While configuring Coupa v.1.0 connector, if you do not want to configure any custom attributes, then enter the value None in the Custom Properties field.

To configure custom attributes:

  1. Enter the custom properties in the mentioned format in Starling.

  2. In the One Identity Manager, map the created custom attributes that were specified in Starling.

  3. Perform a synchronization and verify if the custom attributes are available in the One Identity Manager.

    NOTE:

    • The Starling UI has default mapped attributes.

    • Apart from the default mapped attributes, the Starling UI used for registering a Coupa connector has an input field where you can provide the custom attributes that have to be mapped in the connector's User resource type.

      The format of the custom attributes in the User resource type must be as follows:

      {field_name}|{data_type}

      Example: custom_attribute_name1|string;custom_attribute_name2|string;

      custom_attribute_name1 = name of the custom attribute

      data_type = string (or) boolean

    • All custom attributes are mapped in the enterprise user extensions.

    • All custom user attributes have mutability: readWrite, returned: default, caseExact: false, required: false, 'multiValued: false, uniqueness: none.

    • Only the data types Stringand Boolean are supported currently by Coupa connector.

Configuring custom attributes in connectors

This section describes the steps to configure custom attributes using Starling Connect for connectors.

NOTE:

  • You must first configure custom attributes in the target system before configuring them in Starling Connect.
  • When you are configure custom attributes in Starling Connect, make sure that you provide the custom attribute that you configured in the cloud application because Starling Connect does not perform any validation to check if you have provided a custom attribute that exists in the cloud application.

  • This issue is common for all connectors that allow you to configure custom attributes in Starling Connect.

To configure a custom attribute:

  1. Navigate to the configured connector in the Active Connectors section.
  2. Click the connector tile.

    The General Configuration and Schema Configuration are displayed.

  3. Click EDIT.

    The Schema Configuration displays the Custom Attributes section, where you can configure the custom attributes.

    NOTE: If you have already configured any custom attributes, they are displayed in the Custom Attributes section.

  4.   Select the object under which you want to create the custom attribute.
  5.  In the Custom Attributes section, enter the appropriate values in the following fields:
    • Data Type
    • Target System Attribute name
    • Description

    NOTE:

    Choose the required option from the available list of data types in the Data Type field

    • Binary
    • Boolean
    • DateTime
    • Decimal
    • Integer
    • String
  6. Click SAVE.

    NOTE:

    • To configure another custom attribute, click ADD ATTRIBUTE.
    • To remove a custom attribute, select the custom attribute and click Remove.
    • To modify and existing custom attribute, click the custom attribute and enter new configuration details.
  7. Enter the configuration details in the General Configuration section and click Test Connection.
  8. Click SAVE.

    The newly created custom attribute is displayed in Custom Attributes section and is available in One Identity Manager.

 

NOTE:

  • In SuccessFactors HR connector, if a custom attribute is a part of navigation, then you must enter it in the following format in Starling Connect: <navigation>$$<custom_attribute>. For example, you must enter userNav/dateOfBirth as userNav$$dateOfBirth in Starling Connect.
  • The SuccessFactors HR connector supports single level of navigation only.

 

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택