When creating or modifying authorization profiles, in addition to restricting access to specific features, you can also restrict access to specific PATROL Agents, Computer System Configuration Items (CSCI), devices, and other objects. You specify this granular level of access through the selection of objects on the Objects tab of the Profile Details page.
This topic describes the following information about specifying objects:
Overview of the Objects tab
The Objects tab is where you specify the object restrictions for the authorization profile, as shown in the following image and described the table that follows.
Action menu that enables you to provide unrestricted access to selected object types
When you specify unrestricted access to an object type, you cannot also specify restricted access.
Type of object available in the selected category
Selecting a type filters the list of available objects.
|4||Source||Host name of the Presentation Server or Infrastructure object.|
List of selected objects
To select objects, select the Objects action menu, and select Edit.
For each category, the Objects tab always displays the available types of objects for each category. The data sources determine the objects that exist for a selected type. When you select a category, type, and source, you can then specify individual objects available to the user groups in the authorization profile. The following table lists the types, sources, and objects available for each category.
|Applications||Host name or IP address of the Presentation Server|
|Groups||BMC recommends that as solution administrator when you specify a group type object in an authorization profile, ensure that you include group objects belonging to the same tenant in the authorization profile. For example, there are two objects device-A1 and device-A2 under tenant-A. As a solution administrator, if you want to create a group GA to include device-A1 and device-A2, ensure that the group GA belongs to tenant-A.|
|Monitoring Policy Configuration Types|
|PATROL Agent ACLs||PATROL Agents specified in a PATROL Agent ACL|
|PATROL Solutions||Solutions that can be configured by creating Infrastructure Management|
|CIs||Host name or IP address of Infrastructure Management servers|
How object hierarchy affects monitoring permissions
Providing access to an object enables access to objects that are subordinate to it, as detailed in the following table:
|Object type||Subordinate objects|
|Applications||Devices and groups in the application|
|Devices||Monitor instances under the device|
|Event Groups||Child event groups, and events in the event group and child event groups|
|Sub-groups, devices, and monitor instances in the group|
|Services||Configuration Items in the service|
The following example illustrates how the event group hierarchy affects the monitoring permissions of the users in the authorization profile:
Event group hierarchy:
America is the selected object, then users have access to
America and its child event groups:
North America and
South America. If the selected object is
China, which has no child event groups, then users have access to it. When child event groups will be added under
China, users will have access to them as well.
You cannot specify monitor-level permission in authorization profiles. To provide access to a specific monitor instance under a device, you must create a group, add those monitor instances to the group, and add the group to the authorization profile.
To illustrate how the object hierarchy affects the monitoring permissions of the users in the authorization profile, observe how the objects listed under Selected objects map to the objects listed in Monitoring permissions, which lists the objects that users could access in the TrueSight console.
Group G1, which contains:
Group G2, which contains:
Monitoring instance M1 (from Device D8)
Monitoring instance M2 (from Device D9)
Application A1, which contains:
Application A2, which contains:
|Console page||Accessible objects|
Device D1 (direct permission)
Device D1 (direct permission)