Skip to main content

A Secure Portal Extended With Single Sign-On

Redbooks logo

An IBM Redpaper publication

Other Language Versions

Note: Other language versions may not be as current as the English edition.

Abstract

Many portals are required to access external applications that need some form of user authentication. In most cases, the user credentials required by these applications will differ from those used by WebSphere Portal. While it is possible for the portlet to prompt the user for this credential information and then present it to the external application, such an approach is seldom implemented due to the unsatisfactory user experience. Therefore, a single sign-on (SSO) is required to provide seamless access to the different applications in a portal solution.
Implementing a secure portal using an external security manager is part of solving this problem. This provides a centralized access management system. It is also a basis for creating an SSO domain for multiple applications that can share common user credentials. However, back-end applications can still exist outside of this domain because of a need for specific custom user IDs and passwords. For these, we can use credential mapping to map the common credential to the back-end one. This is implemented as Credential Service in WebSphere Portal.
This publication is intended to help IT architects, IT specialists, security architects, and security administrators with understanding and implementing 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.

Table of contents

Chapter 1. Introduction
Chapter 2. Requirements and Design
Chapter 3. Technology Choices
Chapter 4. Implementing the runtime environment
Chapter 5. Sample Application
Appendix A. Implementing the development environment
Appendix B. Additional material

Profile

Publish Date
24 February 2004


Rating:
(based on 3 reviews)


Author(s)

IBM Form Number
REDP-3743-00