IBM WebSphere V5.0 Security - CGISecurity

Configuring the SSL settings and adding a new entry on a cell level will bereflected in the server’s security settings; but only the configuration issynchronized. It is the administrator’s responsibility to make sure that the keysare copied to the right location for the application servers. It is very important thatthe SSL settings refer to certain directory paths, which are not the same on eachserver, simply because the WebSphere root directory is not (or may not be) thesame on every machine, especially when heterogenous (UNIX, Windows)platforms are attached to the cell.The solution to this problem is to use the WebSphere environment variables inpath definitions on the server level and specify the platform and installationdependent directories there. Once an environment variable with the same nameis defined for each server, you can refer to that variable on the cell level. This iswhat happens when you use the ${WAS_ETC_DIR} variable, for example.For SSL settings, refer to 10.8, “Configuring SSL” on page 258.User registriesThe user registry configured for the cell will be the user registry for each server inthe cell.The user registry for the cell should be a centralized repository, an LDAPDirectory, OS users from a domain, or a custom user registry reading from acentralized, common user repository.For user registry settings, refer to 10.4, “Configuring a user registry” onpage 244.Authentication mechanismsAs mentioned before, in a cell LTPA is the only available authenticationmechanism at the moment.When you configure LTPA for the cell with the deployment manager, you willhave to generate the LTPA key and secure it with a password. The LTPA privateand public keys are stored in the security configuration file, security.xml. Sincethe configurations in this file are synchronized, you do not have to worry aboutdistributing the LTPA keys on each server; the deployment manager will takecare of that.For information on LTPA configuration, refer to 10.6, “LTPA” on page 250.Chapter 10. Administering WebSphere security 341