Creating default registry policy associations

You can use policy associations to create mappings directly between a group of users and a single target user identity.

You want to have all your Microsoft^® Active Directory users on the Windows^® 2000 server map to the user profile SYSUSERA on System A and to the user profile SYSUSERB on System B. In this case, you can create a default registry policy association that maps all the user identities (for which no identifier associations exist) in the MYCO.COM Kerberos registry to a single i5/OS^® user profile on System A.

You need two policy associations to accomplish this goal. Each policy association uses the MYCO.COM user registry definition as the source of the association. However, each policy association maps user identities in this registry to different target user identities, depending on which System i™ platform the Kerberos user accesses:

• One policy association maps the Kerberos principals in the MYCO.COM user registry to a target user of SYSUSERA in the target registry of SYSTEMA.MYCO.COM.

• The other policy association maps the Kerberos principals in the MYCO.COM user registry to a target user of SYSUSERB in the target registry of SYSTEMB.MYCO.COM.

Use the information from your planning works sheets to create two default registry policy associations.

Before you can use policy associations, first enable the domain to use policy associations for mapping lookup operations.

To enable the domain to use policy associations for mapping lookup operations...

1. In iSeries™ Navigator, expand System A > Network > Enterprise Identity Mapping > Domain Management.

2. Right-click MyCoEimDomain, and select Mapping policy.

3. On the General page, select the Enable mapping lookups using policy associations for domain MyCoEimDomain.