Enable embedded ISAM
Embedded Security Access Manager is not enabled by default, and we need to configure it for use.
Enable ISAM security within WebSphere Application Server requires:
- A supported LDAP installed somewhere on the network. This user registry contains the user and group information for both ISAM and WAS.
- ISAM server exists and is configured to use the user registry. For details on the installation and configuration of ISAM, refer to the IBM ISAM for e-business information center.
WAS contains an embedded client for ISAM. To use ISAM, we must also configure the ISAM server.
ISAM server is bundled with WAS.
- WAS is installed either in a single server model or as WAS ND.
- When administrative security is configured with a Federal Information Processing Standard (FIPS) provider, the ISAM server must be configured for FIPS as well
Enable embedded ISAM security:
Tasks
- Create the security administrative user.
- Configure the Java Authorization Contract for Containers (JACC) provider for ISAM .
- Enable WAS security. When using ISAM configure LDAP as the user registry.
- Enable the JACC provider for ISAM.
Enable an external JACC provider Create the security administrative user for ISAM Configure LDAP user registries Enable the JACC provider for ISAM ISAM JACC provider configuration