When modifying an LDAP Policy, the LDAP attributes fields also can be changed: 

GLYPH<SM590000> Base Distinguish Name: The LDAP distinguished name (DN) that uniquely identifies a set of entries in a realm. This field is required but blank by default. The value in this field consists of 1 - 254 Unicode characters. 

GLYPH<SM590000> User Name Attribute: The attribute name that is used for the user name during authentication. This field is required and contains the value uid  by default. The value in this field consists of 1 - 61 Unicode characters. 

GLYPH<SM590000> Password: The attribute name that is used for the password during authentication. This field is required and contains the value userPassword  by default. The value in this field consists of 1 - 61 Unicode characters. 

GLYPH<SM590000> Group Member Attribute: The attribute name that is used to identify group members. This field is optional and contains the value member by default. This field can contain up to 61 Unicode characters. 

GLYPH<SM590000> Group Name Attribute: The attribute name that is used to identify the group during authorization. This field is optional and contains the value cn  by default. This field can contain up to 61 Unicode characters. 

GLYPH<SM590000> User Name filter: Used to filter and verify the validity of an entered user name. This field is optional and contains the value ( uid={0} ) by default. This field can contain up to 254 Unicode characters. 

GLYPH<SM590000> Group Name filter: Used to filter and verify the validity of an entered group name. This field is optional and contains the value ( cn={0} ) by default. This field can contain up to 254 Unicode characters. 

Click OK  to complete the operation. Click Cancel  to abandon the operation and return to the Security Settings window. 

## Creating a RACF based LDAP Policy 

This process is similar to the process that is described “Adding a Direct LDAP policy” on page 472 . Some configurations are required on the host side regarding the RACF, SDBM, and IBM Security Directory Server that must be performed in advance before this capability can be enabled. 

For more information about the parameters and configurations, see Chapter 10, “z Host Console operations” on page 589. When those configurations are ready, the RACF based LDAP Policy can be created and activated. 

Adding a RACF policy is shown in Figure 9-73 on page 474. 

