Customizing SSO configuration using LTPA cookies for the Liberty profile

With single sign-on (SSO) configuration support, web users can authenticate once when accessing Liberty profile resources such as HTML, JavaServer Pages (JSP) files, and servlets, or accessing resources in multiple Liberty profile servers that share the same Lightweight Third Party Authentication (LTPA) keys.

Example

When a user passes authentication on one of Liberty profile servers, authentication information generated by the server is transported to the web browser in a cookie. The cookie is used to propagate the authentication information to other Liberty profile servers.

The LTPA is configured and ready for immediate use. The default cookie name used to store the SSO token is called ltpaToken2. If you want to use a different name for the cookie, you can customize the cookie name using the ssoCookieName attribute of <webAppSecurity> element. If you customize the cookie name, make sure that all the servers that participate in SSO use the same cookie name.

For more information about SSO, see SSO concept in the Liberty profile.

The following example code sets the user to be logged out after the HTTP session expires and the name of the SSO cookie as myCookieName.

  <webAppSecurity  logoutOnHttpSessionExpire=”true”  ssoCookieName=”myCookieName” />

Note: For SSO to work across servers, the Liberty profile servers must have the same LTPA keys and shared the same user registry.

For details of all the available SSO settings, see the <webAppSecurity> element in Liberty profile: Configuration elements in the server.xml file.

Task topic

Terms and conditions for information centers | Feedback

Timestamp icon

Last updated: Wednesday, 22 May 2013
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=twlp_sec_sso
File name: twlp_sec_sso.html