The custom target system objects are mapped in the following tables of the One Identity Manager schema.
Table 2: Tables in the One Identity Manager schema for mapping custom target systems
UNSAccountB |
User account mapping. |
UNSAccountBHasUNSGroupB |
Group assignments to user accounts. |
UNSAccountBHasUNSGroupB1, UNSAccountBHasUNSGroupB2, UNSAccountBHasUNSGroupB3 |
Assignments of system entitlements to user accounts. |
UNSAccountBHasUNSItemB |
Permissions control assignments to user accounts. |
UNSAccountBInUNSGroupB |
Assignments of user accounts to groups. |
UNSAccountBInUNSGroupB1, UNSAccountBInUNSGroupB2, UNSAccountBInUNSGroupB3 |
Assignments of user accounts to system entitlements. |
UNSContainerB |
Container structure mapping. |
UNSGroupB |
Group mapping. |
UNSGroupB1, UNSGroupB2, UNSGroupB3 |
Mapping of other system entitlements. |
UNSGroupBHasUnsItemB |
Permissions control assignments to groups. |
UNSGroupBInUNSGroupB |
Assignments of groups to groups (group hierarchy). |
UNSGroupB1InUNSGroupB1, UNSGroupB1InUNSGroupB2, UNSGroupB1InUNSGroupB3 |
Assignments of system entitlements to system entitlements (system entitlement hierarchy). |
UNSItemB |
Mapping of additional permissions controls. |
UNSRootB |
Basis for mapping custom target systems. |
One Identity Manager provides predefined processes for provisioning data in a custom target system. The processes use scripts for provisioning the data. Provisioning data from One Identity Manager into the custom target system must be customized because each custom target system maps the data differently.
To use scripted provisioning procedures, the following steps are required:
-
Create the provisioning script
Scripts are used to provision data from the One Identity Manager in a custom target system. These must be created for each target system.
-
Provide a server for provisioning
On the server, the One Identity Manager Service must be installed, configured, and started. The server must be declared in One Identity Manager and entered as the synchronization server in the target system.
-
Set up custom target systems in the One Identity Manager database and customize synchronization methods in the One Identity Manager database.
Select the Synchronization by script synchronization method.
In One Identity Manager, default installation processes for the default events are made available for tables, which are used for mapping custom target systems. The processes use scripts for data provisioning. The scripts must be modified to fit the custom target system because each custom target system maps the data differently.
Create custom scripts for your target system. You can use the TSB_Uns_Generic_Templates script as a template for creating custom scripts.
The processes expect scripts that comply with the following naming convention:
<customer prefix>_<table>_<Ident_UNSRoot>_<event>
Example: Provisioning scripts
CCC_UNSAccountB_<Ident_UNSRoot>_Insert
CCC_UNSAccountB_<Ident_UNSRoot>_Update
CCC_UNSAccountB_<Ident_UNSRoot>_Delete
CCC_UNSAccountBHasUNSGroupB1_<Ident_UNSRoot>_Add
CCC_UNSAccountBHasUNSGroupB1_<Ident_UNSRoot>_Del
IMPORTANT: If your target system contains a hyphen (-) in its name, you must remove it from the <Ident_UNSRoot> part. Otherwise, errors may occur during script processing.
You can define a server for each custom target system, which runs all the One Identity Manager Service actions required for provisioning target system objects. For more information about installing and configuring the One Identity Manager Service, see the One Identity Manager Installation Guide.
To set up a server
-
Provide a server installed with the One Identity Manager Service.
-
In the Manager, create an entry for the Job server.
-
Select the Custom Target Systems > Basic configuration data > Servers category.
-
Click in the result list.
-
Edit the Job server's main data.
- Save the changes.
-
Enter the server as the synchronization server in the custom target system.
Detailed information about this topic