Adding new columns for Users using the Schema Extension Tool
This section describes the procedure to add new columns to an existing table for CSMUser.
To add new columns using the Schema Extension Tool for a CSMUser:
- Open Schema Extension tool.
The Select method window is displayed.
- In the Select method window, select Extend Table and click Next.
The Extend Table window is displayed.
- In the Extend Table window, select CSMUser from the Table dropdown list and click Next.
The Configure columns window is displayed.
- In the Configure columns window, create a new column. Name the column appropriately and click Next.
The Access permissions window is displayed.
- In the Access permissions window, define access rights using the options available in the dropdown list and click Next.
- Compile database.
A new column is added.
This section describes the procedure to add new columns to an existing table for UCIUser.
To add new columns using the Schema Extension Tool for a UCIUser:
- Open Schema Extension tool.
The Select method window is displayed.
- In the Select method window, select Extend Table and click Next.
The Extend Table window is displayed.
- In the Extend Table window, select UCIUser from the Table dropdown list and click Next.
The Configure columns window is displayed.
- In the Configure columns window, create a new column.
- Click Next.
The Access permissions window is displayed.
- In the Access permissions window, define access rights using the options available in the dropdown list and click Next.
- Compile database.
A new column is added.
Creating a custom property using Designer tool
The Designer tool is used to create a custom process for CSMUSer and UCIUser.
This section describes the procedure to create a custom process for CSMUser.
To create a custom property for a CSMUser:
- Open Designer.
- Select One Identity Manager Schema.
The One Identity Manager Schema allows you to display and edit the database tables, columns and information.
- Expand Tables and select CSMUser.
- Select Show table definition.
- Navigate to the More tab.
- Select the custom property created.
- Select multi-value column.
- Run Commit to Database.
- Compile the Database.
A custom property is created.
To create a custom property for a UCIUser:
- Open Designer.
- Select One Identity Manager Schema.
The One Identity Manager Schema allows you to display and edit the database tables, columns and information.
- Expand Tables and select UCIUser.
- Select Show table definition.
- Navigate to the More tab.
- Select the custom property created.
- Select multi-value column.
- Run Commit to Database.
- Compile the Database.
A custom property is created.
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.