There are a few things to consider when enabling System Authorization Facility (SAF) authorization for the operating system and application levels.
When SAF authorization is enabled, authorization on any level is always performed by the operating system’s security manager (RACF or an equivalent product). Therefore, it is essential that users are authenticated with a security manager (RACF) user ID. Refer to Summary of controls for more information.
When SAF Authorization is selected during systems customization, administrative EJBROLE profiles for all administrative roles are defined by the RACF jobs generated using the Configuration Dialog. SAF authorization (the use of SAF EJBROLE profiles to assign SAF users and groups to roles) can be used as an authorization mechanism for all user registries. If SAF authorization is selected on the administrative console it overrides any other authorization choice (such as Tivoli Access Manager authorization).
Note that if you do not select Local OS, you must configure and install a Java Authentication and Authorization Service (JAAS) login module to perform principal mapping that maps LDAP or custom registry principal to a SAF user ID.
Note that SAF authorization is also supported for non-Local OS registries. If you turn on SAF, it becomes the default provider (will handle naming and administration functions). Enable SAF and it becomes the native authorization provider.
For more information, refer to Selecting a user registry.
When using a Local OS Registry, you can control access to console users .
If you decide at a future date to turn on SAF authorization, you must issue these RACF commands to enable proper WebSphere Application Server operation. (Change the value of the configured default user ID if you have chosen a different unauthenticated user ID.)