Mapping custom properties using the Synchronization Editor
The Synchronization Editor is used to map the newly custom created property from One Identity Manager to the target system.
To map the newly created custom property from One Identity Manager to the target system:
- Open Synchronization Editor.
- Create a synchronization project for Box connector.
- Map the newly created custom property from One Identity Manager to additionalEmails under extensions at target system side.
- Run the synchronization.
- The additional emails IDs of users are synchronized with One Identity Manager.
You can now create new users with additional email IDs or modify the existing users to add additional email IDs.
One Identity Manager E2E integration needs for Hideez 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
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:
-
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.
-
To configure the custom attributes in Starling UI, enter the Custom Properties in the specified format in the Starling Platform.
-
On the One Identity Manager, map the created custom attributes that were specified in the Starling Platform.
-
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
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:
-
Enter the custom properties in the mentioned format in Starling.
-
In the One Identity Manager, map the created custom attributes that were specified in Starling.
-
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.
