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.

8. The changes will need to be saved and <strong>WebSphere</strong> restarted.10.5 SWAMThe SWAM (Simple <strong>WebSphere</strong> Authentication Mechanism) is intended forsimple, non-distributed, single application server type runtime environments. Thesingle application server restriction is due to the fact that SWAM does notsupport forwardable credentials. For more information on authenticationmechanisms, refer to “Authentication mechanisms” on page 224.Using SWAM does not require further configuration for <strong>WebSphere</strong> ApplicationServer V5; you can simply select SWAM as the authentication mechanism on theGlobal <strong>Security</strong> page, as shown in Figure 10-13.Figure 10-13 Configuring SWAM for the application serverOnce you enable security, <strong>WebSphere</strong> Application Server will use the currentlyset authentication mechanism.10.6 LTPALightweight Third Party Authentication (LTPA) is intended for distributed, multipleapplication server and machine environments. It supports forwardablecredentials, and therefore supports Single Sign-On. LTPA can support security ina distributed environment through the use of cryptography.LTPA requires that the configured User Registry be a central shared repositorysuch as LDAP, a Windows Domain type registry, or a custom user registry.Figure 10-14 Configuring LTPA for the application serverFor more information on authentication mechanisms, refer to “Authenticationmechanisms” on page 224.250 <strong>IBM</strong> <strong>WebSphere</strong> <strong>V5.0</strong> <strong>Security</strong> Handbook

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

Saved successfully!

Ooh no, something went wrong!