Granting Automation Engine Authorizations

As an administrator, when you set up the system, you create and configure User objects. On the Authorizations page in the User object, grant rights to objects, files, execution data, reports, etc.

This page includes the following:

Granting and Denying Authorizations

Rights consist of access permissions and restrictions. The rights of a User are the sum of the authorizations defined on this page and on those that have been granted to the User Groups to which the User has been assigned.

Grant or deny authorizations by specifying first the objects, type of objects or groups of objects and selecting the individual rights the user should have.

* These columns are not displayed by default. To see them, click the arrow on the header row. This opens the list of available columns. The visible ones are marked with a tick, the hidden ones are grayed out. Select the one you need to make it visible; click it again to hide it.

Example

In the User object, you first define Grp. 1 to grant the user Read, Write, and Execution rights on all objects that contain TEST or PRE_PROD in their Name. Then you define Grp.2 to restrict these rights to Agent PSA only.

The user tries to execute the following Jobs (JOBS):

  1. PRE_PROD.JOBS.NO.GRANT not on Agent PSA

  2. TEST.JOBS.GRANT on Agent PSA

The user is denied access to the first job, while the second job ends normally on Agent PSA:

Authorization Filters for Object Attributes

If an object's attribute (such as Login) does not contain a value (""), the wildcard character * is used for comparison with filter lines. If an authorization line contains a particular filter for this attribute (Login), it is still checked.

For example: The object "JOBS.TEST" does not contain a Login object. The following lines are still used in the authorization check:

Grp Type Name Host Login File name (S) Host (D) Login (D) File name (D)
1 JOBS JOBS.TEST * LOGIN.* * * * *
1 JOBS JOBS.TEST * LOGIN.TEST.* * * * *

Required Permissions for Predefined CA Automic Objects

To execute certain predefined CA Automic objects, additional permissions have to be set for their internally referenced Include, PromptSet, and Variable objects.

The names of these objects start with XC_. You grant Users user Read access to them by adding XC_* in the Name field and checking the box in the R column.

Defining Authorizations to Folders and their Contents

Since Folders are also objects, you can use them to collect objects and grant/deny users and user groups permissions to them at folder level.

Take the following into account when defining folder authorizations:

Rights Applicable to Object Types

Each object type has different rights. For example, TimeZone objects cannot be executed, therefore the X-Execute right is ignored.

This table shows the rights you can use for the each object type:

Object type R W X D C S P M
CALE        
CALL
CLNT      
CODE          
CONN        
DASH          
DOCU          
EVNT
FILTER          
FOLD          
HOST  
HOSTG
HSTA          
JOBD
JOBF
JOBG
JOBI        
JOBP
JOBQ
JOBS
JSCH
LOGIN        
PERIOD          
PRPT        
QUEUE  
REPORT              
SCRI
SERV  
STORE          
SYNC  
TZ          
USER    
USRG          
VARA          
XSL          

See also: