Available configurations
On installation, all HCL Workload Automation components
that use the WebSphere Application Server are
configured for authentication in VMM (Virtual Member Manager) mode.
This creates a Federated User Registry, in which you can choose
to use one or more of the following authentication systems:
- Local operating system - the default authentication system at installation on Windows operating systems
- Pluggable Authentication Module (PAM) - the default authentication system at installation on UNIX, Linux, and AIX® operating systems. Custom is the default authentication system at installation on UNIX and Linux operating systems, and on AIX operating systems, it is called CustomPAM, to differentiate it from the other authentication system supported on AIX called, CustomLAM.
- Loadable Authentication Module (LAM) - CustomLAM is an authentication and identification mechanism for AIX operating systems only.
- LDAP
- File Registry
Note: On AIX,
the CustomPAM authentication system is mutually exclusive with both
the CustomLAM and LocalOS authentication system choices.
If you want to use local OS as the authentication method for the Dynamic Workload Console on UNIX operating systems, perform the steps in Configuring the Dynamic Workload Console to use the local OS or PAM authentication method.
If you choose to enable LDAP, you can use one of the following
servers, for which sample configuration templates are supplied in
this documentation:
- IBM® Tivoli® Directory Server
- Sun Java™ Director Server
- Microsoft Windows Active Directory
- z/OS® Integrated Security Services LDAP Server