Chat now with support
Chat with Support

Identity Manager 8.2.1 - Configuration Guide

About this guide One Identity Manager software architecture Customizing the One Identity Manager default configuration Customizing the One Identity Manager base configuration One Identity Manager schema basics Editing the user interface
Object definitions for the user interface User interface navigation Forms for the user interface Statistics in One Identity Manager Extending the Launchpad Task definitions for the user interface Applications for configuring the user interface Icons and images for configuring the user interface Using predefined database queries
Localization in One Identity Manager Process orchestration in One Identity Manager
Mapping processes in One Identity Manager Setting up Job servers
The One Identity Manager Service functionality Tracking changes with process monitoring Conditional compilation using preprocessor conditions Scripts in One Identity Manager
Visual Basic .NET scripts usage Notes on message output Notes on using date values Tips for using Windows PowerShell scripts Using dollar ($) notation Using base objects Calling functions Pre-scripts for use in processes and process steps Using session services Using #LD-notation Script library Support for processing scripts in the Script Editor Creating and editing scripts in the Script Editor Copying scripts in the Script Editor Testing scripts in the Script Editor Testing script compilation in the Script Editor Overriding scripts Permissions for running scripts Editing and testing script code with the System Debugger Extended debugging in the Object Browser
One Identity Manager query language Reports in One Identity Manager Adding custom tables or columns to the One Identity Manager schema Web service integration One Identity Manager as SCIM 2.0 service provider SOAP Web Service One Identity Manager as SPML provisioning service provider Processing DBQueue tasks One Identity Manager Service configuration files

Web service integration

One Identity Manager offers you the option to integrate web services. For example, you can use web services to write data to applications, which cannot be connection to One Identity Manager as a default target system.

Data for external applications can be originate from any of the One Identity Manager schema's tables. They can, for example, be mapped as custom target systems.


The general data for a telephone system should be found from personnel data in One Identity Manager. The telephone system is mapped in One Identity Manager as a custom target system. One extension in the telephone corresponds a user account in One Identity Manager.

Once a new employee has been added in One Identity Manager, a new extension should become available in the telephone system. A new user account is added for each account definition. A web service passes the user account''s main data onto the telephone system. where a new participant and telephone number is added. The web service passes this telephone number to One Identity Manager as the return value. The telephone number should be transferred to the employee's main data.

Proceed as follows

  1. Set up a custom target system in One Identity Manager.

    • Select Scripted synchronization for the Synchronized by property.

  2. Set up the server for provisioning the data.

    • Enter the server as the synchronization server in the custom target system.

  3. Set up an account definition for automatic administration of user accounts in this target system.

  4. Enter the required IT operating data.

  5. Bind the web service to One Identity Manager. Use the generic web service call for this.

    The web service integration wizard helps you to create scripts for provisioning data for the Insert, Update, and Delete default events. The provisioning processes are supplied by default through One Identity Manager.

  6. Create additional scripts and processes for handling the web service return value.

    TIP: When you insert, change, or delete containers, user accounts, and groups in a custom target system, the return values are saved by default as GUID objects in the database.

    Create a process to add the telephone number from the object GUID to the employee main data.

For detailed information about setting up a custom target system, about account definitions, IT operating data and setting up a server, see the One Identity Manager Administration Guide for Connecting to Custom Target Systems.

Detailed information about this topic

Binding a web service

Create a custom script for integrating a web service into One Identity Manager. There is a wizard available to assist you. The Web Service Integration Wizard finds all the methods used by the web service and creates scripts to call the required methods. The data from One Identity Manager is passed as parameters to the method. Which operations in the external application can be run, is determined by the methods defined in the web service. The wizard created new entries in the DialogWebService and DialogScript tables.

The Web Service Integration Wizard supports different types of method calls. Each type supports the method call definition and, therefore, script creation to different degrees.

Generic web service call

You use the generic web service call to publish data from a custom target system to an external application through a web service. The Web Service Integration Wizard queries all the required parameters and generates scrips from them.


The external application data is mapped in One Identity Manager as a custom target system.

  • A custom target system is set up (UNSRootB table). The Synchronized by property has the value Scripted synchronization.

  • A server for provisioning data is set up and stored as synchronization server in the custom target system.

For detailed information about setting up scripted provisioning, see the One Identity Manager Target System Base Module Administration Guide.

Default processes

One Identity Manager supplies default processes for provisioning data from custom target system to a web service.

To use these processes, the scripts you generated with the Web Service Integration Wizard must follow the naming convention:

<Customer prefix>_<table>_<Ident_UNSRoot>_<event>.

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.

Some of these processes handle the web service return values.

Table 178: Default processes for synchronizing by script
Object in custom target system (table) Process Saving the return value

Container (UNSContainerB)



User accounts (UNSAccountB)









Groups (UNSGroupB)









Permissions controls (UNSItemB)















Direct web service call

The Web Service Integration Wizard finds all parameters that are defined in the method and from it, generates the script code. The parameters are passed in the function call You can modify the parameters.

To run a script

  • Create custom processes and pass the scripts and parameters to the process step.

Related topics
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating