Understanding single sign-on (SSO) between IBM Lotus Domino and IBM WebSphere Portal
Editor's Note: This white paper is the first in a three-part series on SSO to be published over the next few months. See the second paper, "Configuring single sign-on (SSO) between IBM Lotus® Domino and IBM® WebSphere® Portal®," and the third, "Understanding single sign-on (SSO) between IBM Lotus Domino and IBM WebSphere Portal."
In this article
- SSO Basics
- How the LTPAToken cookie is used between WebSphere Portal and Lotus Domino
- About the author
By Charles Price
This white paper provides an in-depth explanation of how the single sign-on (SSO) feature works between IBM Lotus Domino and IBM WebSphere Portal. Learn the basics of how cookies are written to―and used in―Internet browsers, how the cookies are used to enable SSO, and exactly what is in the token and why it's needed for SSO between two servers. Included are specific details of where the WebSphere Portal and Lotus Domino servers configure each part of the cookie used for SSO, the LTPAToken.
- developerWorks white paper, "Configuring single sign-on (SSO) between IBM WebSphere Portal and IBM Lotus Domino."
- Knowledge Base document #1158269, "Troubleshooting WebSphere Portal, Domino Extended Products, and Domino SSO issues."
- developerWorks Lotus Notes and Domino product page.
- developerWorks WebSphere Portal zone.
- Lotus Notes and Domino wiki.
- WebSphere Portal family wiki.
- developerWorks article, "How to configure SSO with LTPA for IBM Lotus Connections 2.0."