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 on Exploiting the WebSphere Portal V22.214.171.124 programming model.
In this article
- Creating an SSO infrastructure:
- Customizing the credential vault
- Customizing the login behavior
- Working with user management systems
- Adding group support to our example portlet application
Part 1 of this series introduced the overall IBM WebSphere® Portal programming model and showed where you can customize and extend WebSphere Portal. Part 2 described how URLs are generated in WebSphere Portal and how you can leverage the URL generation capabilities in your themes and skins. This part explores the security related APIs and the user management system.
An important task in installing a new portal is to integrate the portal environment with the overall security environment. This article tells how you can achieve single sign-on (SSO) across different servers and environments, and how you can customize the default portal login behavior using the Java™JAAS framework. You learn about the WebSphere Portal user management APIs which enable you to read from and write to the underlying user management system. Finally, you see how to update the calendar and todo sample (used in Part 1) to retrieve specific todos based on the groups to which a member belongs.
This document will be updated periodically and the Portlet Factory development team welcomes your suggestions.
|Article in PDF format||0606_buehler-WP5101_ProgModel_P3.pdf ( HTTP | FTP )||1MB|
|Code sample||CalendarPortletIBM_Part3.zip ( HTTP | FTP )||479 KB|