Using CA AppLogic® › Grid Administration Guide › Role-Based Access Control › Managing Object ACLs

Managing Object ACLs

The following grid objects have an ACL: applications, global catalogs and the grid itself. Access to grid objects which do not have their own ACL is controlled by the ACL of the containing object. For example, access to components is controlled by the ACL of the containing application and access to global catalog classes is controlled by the ACL of the containing catalog. Object ACLs can be manipulated using the CA AppLogic® command line interface (CLI). The CLI can be used to:

• get an ACL – display the owner and all entries
• put an ACL – replace the owner and all entries
• modify an ACL – change the owner, add an entry or remove an entry

Please see the online CLI command line reference for details:

• Application Management
• Catalog Management
• Grid Management

The CA AppLogic® GUI can also be used to modify an application ACL by accessing the Security tab of the application configuration dialog. As with the CLI commands, principals are referenced by their scope, type and name rather than by their principal ID. The principal scope indicates whether the principal is local or global; the principal type indicates whether the principal is a user or group; the principal name is its common human usable name. For example, the local user John is a principal with a scope of local, a type of user and a name of John. The Security tab is shown below.

In the above example, the global group deva is the ACL owner while the ACL members are global group deva with full access level rights, local group admin with control access level rights and local group all with read access level rights.