MKS Implementer 2006 Administration Guide

Configuring MKS Integrity Server ACLs
Implementer and MKS Integrity Integration
Implementer requires an MKS Integrity user ID to proxy all commands sent to
MKS Integrity. MKS recommends you create a new user ID, for example, iSeries, with a
password that does not expire specifically for this purpose. This should be a user ID you
normally do not log in with. Be sure to create the user ID on both your network and in
MKS Integrity. This is also the user ID you define in Implementer as described on page 230.
In MKS Integrity, this user ID requires:
set up in its own unique group, for example, implementer developer group (the
group should include only users who create and modify Implementer change packages)
special privileges set up through the Impersonation ACL to perform work on behalf of
the actual Implementer user for certain commands
On the MKS Integrity Server, user access is controlled by permissions on ACLs through the
Authorization Administration system. The MKS Integrity administrator typically performs
ACL configuration. For details, see the MKS Integrity Server 2006 Administration Guide.
NOTE The following task uses the MKS Integrity Web interface to configure ACLs;
however, you can also use the MKS Integrity Administration Client. If using the
client interface, modify the steps as needed.
To configure the security ACLs for Implementer Server
1 On the MKS Integrity Server, click Start MKS Authorization Administration.
2 Add the following required ACL entries:
mks:impersonate:group:
principle:
Impersonate allowed
mks:im
Admin allowed
IMPORTANT In this example, implementer developer group is the MKS Integrity
group that all Implementer users are a member of. Change this variable to reflect the
group name you created. To avoid compromising your security, use a group other
than the everyone group; by default, all users are part of this group.
Customizing Permissions for the Implementer Change Package Type
This is a required task that restricts users from the ability to modify user defined change
packages outside of Implementer. This is necessary to ensure Implementer change packages
remain synchronous between Implementer and MKS Integrity.
205