02.05.2013 Views

Description - Mks.com

Description - Mks.com

Description - Mks.com

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

ACL (Access Control List)<br />

permissions for MKS Integrity Suite ACL interaction<br />

DESCRIPTION<br />

The ACL (Access Control List) permissions control user access to MKS Integrity Suite functions (in<br />

both MKS Source Integrity and MKS Integrity Manager) by associating development objects and<br />

operations with specific permissions. For example, whenever a user initiates an operation such as<br />

checking a file in or out, Source Integrity queries the ACL database to determine whether the user<br />

has permission to perform the operation. This reference page is provided as a guide to the ACL<br />

permissions.<br />

There are five server-level ACLs shipped by default: mks:aa--controls the Login access to the AA<br />

application for managing the ACLs, mks:aa:mks--controls Read and Update access to the ACLs,<br />

mks:im controls access to Integrity Manager operations, mks:patch controls the Download<br />

permission required for service pack management, and mks:si--controls access to Source Integrity<br />

operations. For the most part, however, you will be working with project ACLs, that control the<br />

permissions for a particular directory. Working with member ACLs is also possible, which control<br />

permissions for specific files -- this would be for those rare circumstances where security on<br />

specific, individual files must be heavily controlled and where the administrative costs are known<br />

and accepted.<br />

The ACL name itself follows a specific hierarchical format:<br />

● The default server-level ACL is named mks:si. All project and member ACLs will inherit<br />

permissions from this one.<br />

● Project-level ACL names include a specific prefix, taking the format<br />

mks:si:project:id:. The project directory is relative to the root of the<br />

Integrity Server.<br />

● Subproject ACLs have the same format as projects, simply appending the subdirectories<br />

using colons (:) instead of slashes.<br />

● Variant project ACLs have a slightly different prefix, taking the format<br />

mks:si:project:devpath::id.<br />

● Member ACLs simply specify the file name in the ACL name, such as<br />

mks:si:project:id::.<br />

● Archive ACLs simply specify the archive name in the ACL name, such as<br />

295 of 457

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!