03.05.2015 Views

IBM WebSphere V5.0 Security - CGISecurity

IBM WebSphere V5.0 Security - CGISecurity

IBM WebSphere V5.0 Security - CGISecurity

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Configuring the SSL settings and adding a new entry on a cell level will be<br />

reflected in the server’s security settings; but only the configuration is<br />

synchronized. It is the administrator’s responsibility to make sure that the keys<br />

are copied to the right location for the application servers. It is very important that<br />

the SSL settings refer to certain directory paths, which are not the same on each<br />

server, simply because the <strong>WebSphere</strong> root directory is not (or may not be) the<br />

same on every machine, especially when heterogenous (UNIX, Windows)<br />

platforms are attached to the cell.<br />

The solution to this problem is to use the <strong>WebSphere</strong> environment variables in<br />

path definitions on the server level and specify the platform and installation<br />

dependent directories there. Once an environment variable with the same name<br />

is defined for each server, you can refer to that variable on the cell level. This is<br />

what happens when you use the ${WAS_ETC_DIR} variable, for example.<br />

For SSL settings, refer to 10.8, “Configuring SSL” on page 258.<br />

User registries<br />

The user registry configured for the cell will be the user registry for each server in<br />

the cell.<br />

The user registry for the cell should be a centralized repository, an LDAP<br />

Directory, OS users from a domain, or a custom user registry reading from a<br />

centralized, common user repository.<br />

For user registry settings, refer to 10.4, “Configuring a user registry” on<br />

page 244.<br />

Authentication mechanisms<br />

As mentioned before, in a cell LTPA is the only available authentication<br />

mechanism at the moment.<br />

When you configure LTPA for the cell with the deployment manager, you will<br />

have to generate the LTPA key and secure it with a password. The LTPA private<br />

and public keys are stored in the security configuration file, security.xml. Since<br />

the configurations in this file are synchronized, you do not have to worry about<br />

distributing the LTPA keys on each server; the deployment manager will take<br />

care of that.<br />

For information on LTPA configuration, refer to 10.6, “LTPA” on page 250.<br />

Chapter 10. Administering <strong>WebSphere</strong> security 341

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!