You can also map your own implementations, such as telephone systems, in One Identity Manager along side native target systems. To manage these target systems with One Identity Manager, create container structures, user accounts and groups.
Define a custom process to swap data between the target system and the One Identity Manager database.
- One Identity Manager provides predefined processes for data provisioning in the default installation. The processes use scripts for data provisioning. Provisioning data from One Identity Manager into the custom target system must be customized because each custom target system maps the data differently.
- Alternatively, you can configure data imports with the "Data Import" program or, in the Synchronization Editor, set up synchronization using the CSV connector. This requires a large amount of customizing.
The One Identity Manager components for managing custom target systems are available if the "TargetSystem | UNS" configuration parameter is set.
The following users are used for setting up and administration of custom target systems.
Table 1: Users
| Target system administrators |
Target system administrators must be assigned to the Target systems | Administrators application role.
Users with this application role:
-
Administer application roles for individual target system types.
-
Specify the target system manager.
-
Set up other application roles for target system managers if required.
-
Specify which application roles for target system managers are mutually exclusive.
-
Authorize other employees to be target system administrators.
-
Do not assume any administrative tasks within the target system. |
| Target system managers |
Target system managers must be assigned to the Target systems | Custom target systems application role or a child application role.
Users with this application role:
-
Assume administrative tasks for the target system.
-
Create, change, or delete target system objects like user accounts or groups.
-
Edit password policies for the target system.
-
Prepare groups to add to the IT Shop.
-
Can add employees who have an other identity than the Primary identity.
-
Configure synchronization in the Synchronization Editor and define the mapping for comparing target systems and One Identity Manager.
-
Edit the synchronization's target system types and outstanding objects.
-
Authorize other employees within their area of responsibility as target system managers and create child application roles if required. |
| One Identity Manager administrators |
-
Create customized permissions groups for application roles for role-based login to administration tools in the Designer as required.
-
Create system users and permissions groups for non role-based login to administration tools in the Designer as required.
-
Enable or disable additional configuration parameters in the Designer as required.
-
Create custom processes in the Designer as required.
-
Create and configure schedules as required.
-
Create and configure password policies as required. |
| Administrators for the IT Shop |
Administrators must be assigned to the Request & Fulfillment | IT Shop | Administrators application role.
Users with this application role:
|
| Administrators for organizations |
Administrators must be assigned to the Identity Management | Organizations | Administrators application role.
Users with this application role:
|
| Business roles administrators |
Administrators must be assigned to the Identity Management | Business roles | Administrators application role.
Users with this application role:
|
One Identity Manager provides predefined processes for data provisioning in the default installation. The processes use scripts for data provisioning. Provisioning data from One Identity Manager into the custom target system must be customized because each custom target system maps the data differently.
Processes are handled by the generic web service. For more detailed information about calling the generic web service, see the One Identity Manager Configuration Guide.
To use this provisioning procedure, the following steps are required:
TIP: Alternatively, you can set up script controlled synchronization using a CSV connector. This requires a large amount of customizing. For detailed information, see the One Identity Manager CSV Connector User Guide.
In One Identity Manager, default installation processes for the standard events (Insert, Update, Delete) 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 functions in the script that are named with the following format:
<customer prefix>_<table>_<Ident_UNSRoot>_<event>
Example: Entering user accounts into the custom "Telephone system" target system
CCC_UNSAccountB_Telephonesystem_Insert
IMPORTANT: If your target system contains a hyphen ("-") in its name, you must remove it from the script function in the <Ident_UNSRoot> part. Otherwise, error may occur during script processing.
The objects in the custom target system are mapped in the following table schema One Identity Manager table.
Table 2: Tables in the One Identity Manager schema for mapping custom target systems
|
UNSAccountB |
User account mapping. |
|
UNSAccountBHasUNSItemB |
Permissions control assignments to user accounts. |
|
UNSAccountBInUNSGroupB |
Group assignments to user accounts. |
|
UNSContainerB |
Container structure mapping. |
|
UNSGroupB |
Group mapping. |
|
UNSGroupBHasUnsItemB |
Permissions control assignments to groups. |
|
UNSGroupBInUNSGroupB |
Group assignments to groups. |
|
UNSItemB |
Mapping of additional permissions controls. |
|
UNSRootB |
Basis for mapping custom target systems. |
