立即与支持人员聊天
与支持团队交流

Identity Manager 8.2 - 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 SOAP Web Service One Identity Manager as SPML provisioning service provider Processing DBQueue tasks One Identity Manager Service configuration files

Permissions for running scripts

The basic permissions for running scripts are granted to the logged in user through the program feature Allow the starting of arbitrary scripts from the frontend (Common_StartScripts).

If a script is assigned a program function (QBMScriptHasFeature table), users can only run this script if they have the necessary permissions groups. An error occurs if the user does not own this program function and tries to run it.

Detailed information about managing permissions and running scripts through program functions can be found in the One Identity Manager Authorization and Authentication Guide.

Editing and testing script code with the System Debugger

The System Debugger gives you the opportunity to test scripts, templates, formatting rules, methods, and table scripts. Visual Studio debug and edit options are available to you.

The following software must be installed to use the System Debugger:

  • Visual Studio 2012 with the current service pack

  • Microsoft .NET Framework Version 4.7.2 Developer Pack or later

NOTE: To use the System Debugger with privileges without starting Visual Studio, you must install the One Identity Manager components in a local directory which is not controlled through user accounts.

Detailed information about this topic

Loading the script library

When you call the System Debugger, a SystemLibrary.sln solution template with the SystemLibrary solution is loaded in theVisual Studio for editing and testing the scripts.

The following projects are defined in the solution.

Table 141: Solution project files
Project Script File Description

Methods

Methods.vb

This script file contains all methods.

Scripts

VIScripts.vb

This script file contains all predefined scripts from the model components.

VIDScripts.vb

This script file contains all predefined scripts from the system components.

CustomerScripts.vb

This script file contains custom scripts. Add new scripts here.

SystemDebugger

Main.vb

Start up project.

Tables

Tables.vb

This script file contains all the table scripts.

Templates

Templates.vb

This script file contains all templates and formatting scripts.

To load the system library

  1. Run the SystemLibrary.sln file in the One Identity Manager installation directory.

  2. Check whether SystemDebugger is entered in Visual Studio as the start project.

  3. Start the solution with F5 in Visual Studio.

  4. Connect to the database.

  5. Check the solution file directory and the options for creating the script library.

    Options Meaning

    Export system scripts

    Specifies whether predefined scripts are loaded into the system library.

    Export custom scripts

    Specifies whether custom scripts are loaded into the system library.

    Export locked scripts

    Specifies whether only active scripts or also locked scripts are loaded from the script library.

    Update project references

    Specifies whether references used in scripts are also loaded.

    Create backups of existing files

    Specifies whether backups of existing files are made.

  6. Click OK.

    The script library files are filled with data from the database.

  7. Confirm reloading of each project in Visual Studio.

  8. Start the solution with F5 in Visual Studio.

    The source code generated for the solution is compiled.

  9. Reconnect to the database.

    Starts the System Debugger.

Related topics

Tips for editing script code in the System Debugger

After loading the system library, you can edit scripts, templates, formatting scripts, methods, and table scripts in the System Debugger and test them.

Note the following:

  • You are not permitted to edit VI-Key comments in the source code or to delete them because they label each code block and are needed for backing up scripts in the database.

  • When templates and formatting scripts are loaded, the $ notation is converted into a GetTriggerValue method call. All GetTriggerValue methods calls are converted into $ notation when the changes are saved in the database.

    Example:

    $FK(UID_Person).IsExternal:Bool$ is converted into GetTriggerValue("FK(UID_Person).IsExternal").Bool when it is loaded

  • In the Designer, you can use the Script Editor to create scripts. Enter the name of the script in the Script Editor and a skeleton script body. This you can export to the script library where you can edit the script with the System Debugger.

  • In the Designer, you can created templates, formatting scripts, methods, and table scripts. You can edit these elements with the System Debugger after you have exported them to the system library.

Related topics
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级