This section provides details on configuring the underlying subsystem for the Roles and Resources tab. Topics include:
After creating the Role Service driver at installation time, you can optionally modify some of the driver configuration settings in iManager. To configure the Role Service driver:
In iManager, click.
Browse to the driver set where the driver exists, then click.
Click the upper-right corner of the Role Service driver icon, then click.
Click on thetab.
Scroll down to thesection of the page.
Make any changes you would like to the settings, and clickto commit your changes.
You can modify the following standard driver settings (listed underon the Driver Configuration page), which get their initial values at installation time:
Table 2-6 Standard Driver Settings
The distinguished name of the User Application driver object that is hosting the role system. Use the eDirectory format, such as UserApplication.driverset.org, or browse to find the driver object. This is a required field.
The URL used to connect to the User Application in order to start Approval Workflows. This is a required field.
The distinguished name of the object used to authenticate to the User Application in order to start Approval Workflows. This needs to a user who has been assigned as a Provisioning Administrator for the User Application. Use the eDirectory format, such as admin.department.org, or browse to find the user.
The identity needs to be entered in LDAP format (for example, cn=admin,ou=department,o=org), rather than dot format. Note that this is different from the format required at driver install time, where dot notation is expected.
This is a required field.
Password of the account specified in the User Application Identity field. The password is used to authenticate to the User Application in order to start approval workflows. This is a required field.
Re-enter the password of the account specified in the User Application Identity field.
In addition, you can modify the following additional settings (listed underon the Driver Configuration page) to customize the behavior of the Role Service driver:
Table 2-7 Additional Settings for Customizing the Role Service Driver
Specifies the number of days the driver should wait before cleaning up request objects that have finished processing. This value determines how long you are able to track the status of requests that have been fulfilled.
Specifies the number of minutes the driver should wait before reevaluating dynamic and nested groups. This value determines the timeliness of updates to dynamic and nested groups used by the User Application. In addition, this value can have an impact on performance. Therefore, before specifying a value for this option, you need to weigh the performance cost against the benefit of having up-to-date information in the User Application.
Determines whether audit events are generated by the driver.
For details on audit configuration, see Section 3.0, Setting Up Logging.
The Role Service driver creates relevant indexes in eDirectory for roles definitions. If you upload a large number of roles, the indexing of these values may take some time. You can monitor these indexes under Index Management in iManager.
Here is the list of Index Names for the indexes created for the Role Service driver:
nrf(Object Class) nrf(nrfMemberOf) nrf(nrfStatus) nrf(nrfStartDate) nrf(nrfNextExpiration) nrf(nrfParentRoles) nrf(nrfChildRoles) nrf(nrfCategory) nrf(nrfRoleCategoryKey) nrf(nrfLocalizedNames) nrf(nrfLocalizedDescrs) nrf(nrfRoles)
The Role Subsystem uses a set of system roles to secure access to functions within thetab. Each menu action in the tab is mapped to one or more of the system roles. If a user is not a member of one of the roles associated with an action, the corresponding menu item is not displayed on the tab.
The system roles are administrative roles automatically defined by the system at install time for the purpose of delegated administration. These include the following:
To assign users to the system roles, you need to use the Section 8.3, Administrator Assignments.action on the tab. For details on assigning users to roles, see
The initial assignment of the Role Administrator is specified at installation time and processed when the Role Subsystem is first initialized at startup time.
By default, the View Request Status action retrieves up to 10,000 request objects. If a user attempts to retrieve a larger result set, the user will see a message indicating that the limit has been reached. In this case, the user should narrow the search (by specifying a particular user or status, for example) to limit the number of objects returned in the result set. Note that when a user applies a filter to a role name, the filter limits what the user sees and its order, not the number of objects returned.
The administrator can change the maximum number of request objects retrieved by modifying the entity definition for the nrfRequest object in iManager. To do this, the administrator needs to modify the <search-max>10000</search-max> setting by editing the XmlData attribute of the sys-nrf-request object. The sys-nrf-request object can be found under EntityDefs.DirectoryModel.AppConfig within the User Application driver for the Roles Based Provisioning Module.
The Administration tab in the User Application provides several settings you can use to control how result sets are processed and displayed on pages within the application. To configure the settings for result sets and pagination:
Open thein the User Application.
Selectfrom the left navigation menu.
Scroll down to thesection of the page.
Modify any of the following settings, and click.
Specifies the default number of rows to display in lists shown on thetab.
When a user initiates a query on any of the pages listed above, the User Application caches the data obtained by the query, and returns the number of rows specified for this setting to the browser. Each time the user requests to see the next page, another set of rows is returned from the cache.
The default value for this setting is 25.
Allows you to specify additional values that the user can select to override the default number of rows displayed on the My Roles, View Request Status, Browse Role Catalog, and Manage Role Relationships pages. The list of values you type must be separated by spaces.
Note that the number specified in thecontrol is always included in the list of values for the user to select.
The default value for this setting is 5 10 50 100 500.
NOTE:This setting also applies to the Team Tasks page on the Work Dashboard tab and to the Object Selector. The default number of rows displayed on the Team Tasks page and in the Object Selector, however, is not controlled by thesetting. The default number of rows for team tasks is set at 5, and the default number of rows for the Object Selector is set at 10.
Specifies the maximum amount of memory (expressed in rows) for the client browser to use for sorting and filtering. If you specify a very high value, client-side sorting and filtering will be very fast, but an excessive amount of memory might be used on the client. If you specify a very low value, the client-side memory usage might be low, but sorting and filtering might also be too slow.
This setting applies only if the size of the result set is less than or equal to the threshold value. If the size of the result set is larger than the threshold value specified, sorting and filtering operations are performed on the server.
The default value for this setting is 1000.
The Role Subsystem uses two templates that are specific to roles-based provisioning:
(Role Request Notification)
(Role Request Approval Completed Notification)
(Resource Request Notification)
(Resource Request Approval Completed Notification)
You can edit the templates to change the content and format of e-mail messages. For more information on these templates, see Section 17.4, Working with E-Mail Templates.
Version 3.7 of the Roles Based Provisioning Module ships with updated configuration files for the following drivers:
SAP User Management
SAP GRC Access Control
All of these updated driver configuration files contain a new section on the driver's Global Configuration Values (GCV) page labeled.
To display the configuration options available in the new section, selectfor the GCV.
To enable resource mapping for the driver, selectfor the GCV.
Depending on the driver's capabilities, one or more lower-level options are displayed once resource mapping is turned on. The Active Directory driver, for example, has three lower-level options:
Each option can be turned on or off individually by selectingor .
After saving the changes and restarting the driver, RBPM will detect the driver as enabled for resource mapping.
You can use lists in request forms to display various options for specifying a resource assignment. This section provides instructions for adding lists to the database by executing a few SQL statements. Once these lists have been created, they can be displayed on a request form on the Roles and Resources tab.
The following example shows how you would create a simple set of values for a list. This example uses SQL statements that work with MySQL:
INSERT INTO PROVISIONING_CODE_MAP SET VIEWID='Factory-Locations', VERSIONNO=1, DESCRIPTION='Factory Locations', NAME='Factory Locations',ENTITYKEY='Factory-Locations', ENTITYTYPE=1, LASTREFRESHED=UNIX_TIMESTAMP(); INSERT INTO PROVISIONING_VIEW_VALUE SET VALUEID='Factory-Locations-1', VERSIONNO=1, VIEWID='Factory-Locations', PARAMVALUE='Cambridge, MA 02440'; INSERT INTO PROVISIONING_VIEW_VALUE SET VALUEID='Factory-Locations-2', VERSIONNO=1, VIEWID='Factory-Locations', PARAMVALUE='Provo, UT 97288';
For PostgreSQL, the syntax would be the same except that you would need to replace UNIX_TIMESTAMP() with epoch.
The VIEWID is the primary key for the PROVISIONING_CODE_MAP. The ENTITYTYPE value 1 identifies the map type as a list. The VIEWID is the foreign key for the PROVISIONING_VIEW_VALUE relationship to the PROVISIONING_CODE_MAP table. The VALUEID is the primary key for the PROVISIONING_VIEW_VALUE table.
After the Company Location field has been added to the form, you can specify that the company location value should come from the Company Locations list at request time:
After the Factory Location field has been added, you can specify that the factory location value must come from the Factory Locations list at request time:
At request time, the user can then select the company location and factory location values when assigning the resource:
After the resource has been assigned, the Request Status tab for the resource displays the parameter values chosen from the lists for the request form fields: