Chat now with support
Chat with Support

Identity Manager 9.3 - Authorization and Authentication Guide

About this guide One Identity Manager application roles Granting One Identity Manager schema permissions through permissions groups Managing permissions to program functions One Identity Manager authentication modules OAuth 2.0/OpenID Connect authentication Multi-factor authentication in One Identity Manager Granular permissions for the SQL Server and database Installing One Identity Redistributable Secure Token Server Preventing blind SQL injection Program functions for starting the One Identity Manager tools Minimum access levels of One Identity Manager tools

Permissions for running scripts

The basic permissions for running scripts are granted to the logged in user by the Common_StartScripts program function.

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.

To control how a script is run using a program function

  1. Create a new program function.

    1. In the Designer, select the Permissions > Program functions category.

    2. Select the Object > New menu item.

    3. Enter the following information:

      • Program function: Name of the program function.

      • Description: Short description of the program function.

      • Function group: Property for grouping program functions.

  2. Connect the program function with the scripts that the user are allowed to trigger.

    1. In the Designer, select the Permissions > Program functions category.

    2. Select the View > Select table relations menu item and enable the QBMScriptHasFeature table.

    3. In the List Editor, select the newly created program function.

    4. In the Scripts edit view, assign the scripts.

  3. Assign the required program functions to the custom permissions group whose systems users will run these scripts.

    1. In the Designer, select the Permissions > Program functions category.

    2. Select the View > Select table relations menu item and enable the DialogGroupHasFeature table.

    3. In the List Editor, select your newly created program function.

    4. In the List Editor, use Ctrl + select to select your new program function and the Common_StartScripts program function.

    5. Assign the permissions group in the Permissions groups edit view.

  4. Select the Database > Save to database and click Save.

Related topics

Permissions for running methods

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

To make a task definition available to users using a program function

  1. Create a new program function.

    1. In the Designer, select the Permissions > Program functions category.

    2. Select the Object > New menu item.

    3. Enter the following information:

      • Program function: Name of the program function.

      • Description: Short description of the program function.

      • Function group: Property for grouping program functions.

  2. Connect the program function with the task definition events that the user will trigger.

    1. In the Designer, select the Permissions > Program functions category.

    2. Select the View > Select table relations menu item and enable the QBMMethodHasFeature table.

    3. In the List Editor, select the newly created program function.

    4. In the Tasks edit view, assign the task definitions.

  3. Assign the program functions to the custom permissions group whose systems users will run these scripts.

    1. In the Designer, select the Permissions > Program functions category.

    2. Select the View > Select table relations menu item and enable the DialogGroupHasFeature table.

    3. In the List Editor, select your newly created program function.

    4. Assign the permissions group in the Permissions groups edit view.

  4. Select the Database > Save to database and click Save.

Related topics

Permissions for triggering processes

The basic permissions for triggering processes are granted to the logged in user by the Common_TriggerEvents program function.

In One Identity Manager, triggering of events on stored processes is linked to the permissions concept. Users can only trigger events on objects like this if they own edit permissions for them. This can lead to table users who only have viewing permissions not being able to trigger additional events for processes.

In this case, it is possible to connect the object events (QBMEvent table) with a program function (QBMFeature table). An event (JobEventGen table), which is defined for a process, is linked with an object event (JobEventGen.UID_QBMEvent column). The object events are linked to a program function (QBMEventHasFeature table). Users with this program function can trigger the object event and therefore the process too independent of their permissions.

The Common_TriggerSpecificEvents program function allows you to trigger specific events from the front-end. You can assign this program function to custom object events that any user can trigger. The program function is allocated to the QBM_BaseRigt permissions group.

To control triggering a process through a program function

  1. Create a new program function.

    1. In the Designer, select the Permissions > Program functions category.

    2. Select the Object > New menu item.

    3. Enter the following information:
      • Program function: Name of the program function.

      • Description: Short description of the program function.

      • Function group: Property for grouping program functions.

  2. Connect the program function with object events that the user will trigger.

    1. In the Designer, select the Permissions > Program functions category.

    2. Select the View > Select table relations menu item and enable the QBMEventHasFeature table.

    3. In the List Editor, select the newly created program function.

    4. In the Object events edit view, assign the object events.

  3. Assign the required program functions to the custom permissions group whose systems users will trigger these events.

    1. In the Designer, select the Permissions > Program functions category.

    2. Select the View > Select table relations menu item and enable the DialogGroupHasFeature table.

    3. In the List Editor, use Ctrl + select to select your new program function and the Common_TriggerEvents program function.

    4. Assign the permissions group in the Permissions groups edit view.

  4. Select the Database > Save to database and click Save.

Related topics

Modifying permissions for running actions in the Launchpad

One Identity Manager supplies a number of Launchpad actions that you can use to start applications by using the Launchpad. You can also start your own applications over the Launchpad.

If some actions in the Launchpad should not be made available to all users, you can manage the permissions by assigning Launchpad actions to program functions (QBMLaunchActionHasFeature table). Only tasks containing actions that the user's program function permissions permit him to run are shown in the Launchpad.

To assign a program function to Launchpad actions

  1. In the Designer, select the Permissions > Program functions category.

  2. Select the View > Select table relations menu item and enable the QBMLaunchActionHasFeature table.

  3. In the List Editor, select the program function.

  4. In the Launchpad action edit view, assign the actions.

  5. Select the Database > Save to database and click Save.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating