In order to use a pluggable login module to perform Java 2 Platform, Enterprise edition (J2EE) identity to Resource Access Control Facility (RACF) user mapping, a pluggable mapping module followed by a WebSphere Application Server for zOS-supplied module must be configured in appropriate Java Authentication and Authorization Service (JAAS) system login configurations. This enables an installation to configure the active WebSphere Application Server user registry as either Lightweight Directory Access Protocol (LDAP) or a Custom registry and use System Authorization Facility (SAF) authorization.
Before proceeding you should make sure you know how to write a mapping module to get a SAF identity. For more information, refer to Writing a custom System Authorization Facility mapping module for WebSphere Application Server . If you use anything other than the sample, you must build the relevant classes and install it into the <WAS_HOME>/classes directory for each node in the cell, including the deployment manager node in a Network Deployment cell. If Java 2 security is enabled, ensure that the server.policy file is updated to provide appropriate permissions.
The custom SAF mapping module (either com.ibm.websphere.security.SampleSAFMappingModule or a customer-written mapping module) must be added to each of the system login module entries below, and must be changed to the second to last position in the order manually for the system login modules as indicated below.
Note: For base configuration, if you select SWAM as your authentication mechanism, update the SWAM_ZOSMAPPING entry. However, if you plan to use LTPA as your authentication mechanism, set up all four system login module entries. For an ND configuration you only need to configure the LTPA authentication mechanism configuration entries.
To add a custom SAF mapping module to one of the system login modules listed above, log on to the administrative console application and:
Note: If the SAF identity mapping module you installed has configurable properties, you can update them by creating custom properties in the system login panel in the administrative console. Use this example to update properties if you used the SampleSAFMapping module as a prototype and updated the else clause to provide custom mapping logic. In this case you must create the useWSPrincipleName custom property and set it to false for each affected JAAS login configuration that uses the modified SampleSAFMappingModule.
Repeat this process for each of the system login modules that use the modified SampleSAFMappingModule.
For more information, refer to: