Skip to main content link. Accesskey S
  • Log In
  • Help
  • IBM Logo
  • WebSphere Portal Family wiki
  • All Wikis
  • All Forums
  • Home
  • Product Documentation
  • Community Articles
  • Learning Center
  • IBM Redbooks
Community Articles Product Documentation Learning Center IBM Redbooks This category IBM Redbooks: Building a Sample Website Using IBM Web Content Manager 7.0 IBM Redbooks: Building and Implementing a Social Portal IBM Redbooks: Developing Exceptional Multi-Channel Web Experiences V7: IBM Web Content Manager Product Documentation V7: IBM WebSphere Portal Enable for z/OS Product Documentation V7: IBM WebSphere Portal Express Product Documentation V7: WebSphere Portal Product Documentation V8: IBM Web Content Manager Product Documentation V8: IBM WebSphere Portal Express Product Documentation V8: IBM WebSphere Portal Product Documentation (includes z/OS) Custom Search Scope...
Search
Community Articles > WebSphere Portal > Setting up single sign-on for WebSphere Application Server
  • New Article
  • Share Show Menu▼
  • Subscribe Show Menu▼

About the Original Author

IBM contributorDon Naro
Contribution Summary:
  • Articles authored: 33
  • Articles edited: 104
  • Comments Posted: 6

Recent articles by this author

Composite Application Infrastructure

This video demonstrations showcases the Composite Application Infrastructure in IBM WebSphere Portal. The demo highlights different Composite Application features and introduces a range of use cases, including runtime scenarios, community scenarios, and template scenarios.

Setting up single sign-on for WebSphere Application Server

Set up single signon (SSO) between two or more instances of IBM® WebSphere® Application Server so users can authenticate to all applications running on WebSphere Application Server with a single log in. For example, you can set up SSO on WebSphere Application Server to enable single ...

IBM Retail Vendor template for WebSphere Portal presentation

The IBM Retail Vendor template for WebSphere Portal presentation, attached to this article, provides detailed information on the features and system architecture of the Retail Vendor template. Download the presentation to learn more about the Retail Vendor template.

IBM Retail Vendor template, Vendor User Management

This video demonstration provides an overview of the Vendor User Management portlet with the IBM Retail Vendor template for WebSphere Portal.

IBM Retail Vendor template, User registration and onboarding

This video demonstration shows how users register and onboard with the IBM Retail Vendor template for WebSphere Portal.

Community articleSetting up single sign-on for WebSphere Application Server

Added by Don Naro | Edited by IBM contributor Don Naro on October 5, 2010 | Version 9
  • Edit
  • More Actions Show Menu▼
Rate this article 1 starsRate this article 2 starsRate this article 3 starsRate this article 4 starsRate this article 5 stars
expanded Abstract
collapsed Abstract
Set up single sign-on (SSO) between two or more instances of IBM® WebSphere® Application Server so users can authenticate to all applications running on WebSphere Application Server with a single log in. For example, you can set up SSO on WebSphere Application Server to enable single authentication sessions between IBM WebSphere Portal and IBM WebSphere Process Server or between WebSphere Portal and IBM Lotus Quickr for WebSphere Portal. SSO on WebSphere Application Server is established through Lightweight Third Party Authentication (LTPA) keys. You export the LTPA key from one instance of WebSphere Application Server then import that key into a different instance of WebSphere Application Server to establish SSO.
Tags: Lotus Quickr, Process Server, WAS, WebSphere Portal, single sign-on, SSO
ShowTable of Contents
HideTable of Contents
  • 1 Enabling single sign-on
  • 2 Exporting the LTPA key
  • 3 Importing the LTPA key
  • 4 Verifying single sign-on
Important: Synchronize the time on each instance of WebSphere Application Server for which you plan to set up SSO. LTPA tokens use timestamps from the server to timeout. SSO failures can occur because the time difference between servers is greater than the timeout value of the LTPA tokens.

Enabling single sign-on



Enable single sign-on (SSO) on all the instances of WebSphere Application Server for which you plan to establish SSO.

To enable SSO on WebSphere Application Server, do the following:

1. Log in to the WebSphere Application Server administration console.
2. Navigate to Security > Global Security.
3. In the Authentication cache settings section, expand Web and SIP security then select Single sign-on (SSO).
4. In the General Properties section, specify the following configuration values for single sign-on:

Enabled
Selected by default.

Requires SSL
Specify the domain name that you are using for the servers; for example, my.companyname.com.

Interoperability Mode
Select this field if not selected by default.

Web inbound security attribute propagation
Selected by default.

5. Click OK and save to the master configuration.

Repeat the preceding steps for the other instances of WebSphere Application Server for which you plan to establish SSO.

Exporting the LTPA key



Export a Lightweight Third Party Authentication (LTPA) key from WebSphere Application Server to import into other instances of WebSphere Application Server. You only need to export the LTPA key from one server.

Before you begin:

i. Enable SSO on WebSphere Application Server.

To export the single sign-on key, do the following:

1. Log in to the WebSphere Application Server administration console.
2. Navigate to Security > Global security > Authentication > LTPA.
3. In the Cross-cell single sign-on section, specify a password for the LTPA key.
4. Enter the LTPA key name and directory to which you want to export the key in the Fully qualified key file name field. For example, on Windows, enter C:\my_key_name on Linux, enter /opt/my_key_name.
5. Click Export keys.
6. Click OK and save to the master configuration.
7. Navigate to the directory where you exported the LTPA key.
8. Copy the LTPA key to the file system where you plan to import it.

Importing the LTPA key



Import the LTPA key into WebSphere Application Server. You can import the same LTPA key into multiple servers.

Before you begin:

i. Export the LTPA key.
ii. Copy the LTPA key from the file system where you exported it to the file system where you plan to import it.

To import the LTPA key, do the following:

1. Log in to the WebSphere Application Server administration console.
2. Navigate to Security > Global security > Authentication > LTPA.
3. In the Cross-cell single sign-on section, specify the password for the LTPA key.
4. Enter the directory on your file system where you copied the LTPA key in the Fully qualified key file name field.
5. Click Import keys.
6. Click OK and save to the master configuration.
7. Restart both the server you exported the LTPA key from and the server into which you imported the LTPA key. Restart the servers only after you have imported the LTPA key into all the servers for which you plan to establish SSO.

Repeat the steps in this task for all servers for which you plan to set up SSO, then restart all servers.

Verifying single sign-on



You have successfully established SSO between multiple instances of WebSphere Application Server when you can log in to one administration console then access the other administration consoles without having to log in again.

To verify SSO, do the following:

1. Log in to the WebSphere Application Server administration console where you exported the LTPA key.
2. In your browser's address bar, enter the URL for the WebSphere Application Server administration console where you imported the LTPA key.

If the WebSphere Application Server administration console opens without requiring you to log in, you have successfully set up SSO.

  • Edit
  • More Actions Show Menu▼


expanded Attachments (0)
collapsed Attachments (0)
Edit the article to add or modify attachments.
expanded Versions (9)
collapsed Versions (9)
Version Comparison     
VersionDateChanged by              Summary of changes
This version (9)Oct 5, 2010 10:16:58 AMDon Naro  IBM contributor
8Oct 5, 2010 9:55:10 AMDon Naro  IBM contributor
7Sep 20, 2010 9:52:06 AMDon Naro  IBM contributor
6Sep 20, 2010 9:51:16 AMDon Naro  IBM contributor
5Sep 20, 2010 9:50:19 AMDon Naro  IBM contributor
4Sep 20, 2010 9:48:56 AMDon Naro  IBM contributor
3Sep 20, 2010 9:47:38 AMDon Naro  IBM contributor
2Sep 20, 2010 9:45:09 AMDon Naro  IBM contributor
1Sep 20, 2010 9:40:06 AMDon Naro  IBM contributor
expanded Comments (0)
collapsed Comments (0)
Copy and paste this wiki markup to link to this article from another article in this wiki.
Go ElsewhereStay ConnectedHelpAbout
  • IBM Collaboration Solutions wikis
  • IBM developerWorks
  • IBM Software support
  • Twitter LinkIBMSocialBizUX on Twitter
  • FacebookIBMSocialBizUX on Facebook
  • ForumsLotus product forums
  • BlogsIBM Social Business UX blog
  • Community LinkIBM Collaboration Solutions
  • Wiki Help
  • Forgot user name/password
  • Wiki design feedback
  • Content feedback
  • About the wiki
  • About IBM
  • Privacy
  • Accessibility
  • IBM Terms of use
  • Wiki terms of use