WebSphere Portal Security, Login, and Single-Sign-On

A Secure Portal Extended With Single Sign-On
IBM Redpaper (REDP-3743-00) - Understand and implement a secure portal with SSO. This publication is built on and extends A Secure Portal Using WebSphere Portal V5 and Tivoli Access Manager V4.1, SG24-6077.

A Secure Portal Using WebSphere Portal V5 and Tivoli Access Manager V4.1
Redbook SG24-6077-00

Configuring a different login attribute after the security is enabled
Normally when changing Lightweight Directory Access Protocol (LDAP) server configurations, IBM support recommends the process of disabling security and re-enabling with new settings. In some special cases, using the standard configuration task is not sufficient. This IBM Technote (FAQ) provides guidance.

Exploiting the WebSphere Portal V5.1.0.1 programming model: Part 3: Integrating WebSphere Portal into your security environment and user management system
Use the portal programming interfaces to implement single sign-on (SSO), customize portal login behavior, and work with the user profiles. See the interfaces applied to the calendar and todo example from Part 1. This is the third part in an article series.

How to log in to WebSphere Portal when users have identical login attributes
When trying to log in to the portal server using an attribute for which duplicate entries in the LDAP exist (such as cn), you receive the following error: SECJ0373E: Cannot create credential for the user due to failed validation of the LTPA token. - IBM Technote (FAQ)

Must the login attribute be unique across all realms in a multiple realm environment?
Does the login attribute have to be unique across all realms? This IBM Technote (FAQ) answers.

PORTAL 6 SSO with Windows Desktop
discussion thread

Securing Your Collaborative Portal Using WebSeal
Redbook Technote: TIPS0331