13.07.2015 Views

IBM WebSphere V5.0 Security - CGISecurity

IBM WebSphere V5.0 Security - CGISecurity

IBM WebSphere V5.0 Security - CGISecurity

SHOW MORE
SHOW LESS
  • No tags were found...

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

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

In the previous steps, we assumed that the user registry is already configuredfor LDAP. Configuring the User Registry is covered in previous sections. LTPAalso works with other user registries; only this example uses LDAP, but forSingle Sign-On scenarios, you might want to use centralized user registries.Note: The generation of the LTPA keys must be performed when the LDAPserver settings are configured; this guarantees that the LDAP hostname ispresent in the exported file, as shown in bold in Example 10-1 onpage 254. Domino needs this information during the Web SSOConfiguration Document creation process.3. Save the configuration.Your <strong>WebSphere</strong> Application Server is now configured to use LTPAauthentication mechanism. You will need to log out of the Administrative Consoleand restart the server in order for the changes to take effect.10.7 JAAS configurationJAAS for <strong>WebSphere</strong> Application Server can be configured using theAdministrative Console. JAAS provides the pluggable authentication mechanismfor <strong>WebSphere</strong>. If you want to know more about JAAS, refer to 8.6, “JAAS” onpage 204.10.7.1 Application login information<strong>WebSphere</strong> allows you to configure the pluggable authentication module for yourapplication server.1. Launch the Administrative console then log in with administrative privileges.2. Select <strong>Security</strong> -> JAAS Configuration -> Application Logins to get to thepage show in Figure 10-16.Chapter 10. Administering <strong>WebSphere</strong> security 255

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

Saved successfully!

Ooh no, something went wrong!