Summary

In this tutorial, you have learned to use the following WebSphere Application Server and Tivoli Access Manager scenarios:

1. You've shared a user registry between Access Manager and WebSphere. Both components used the same LDAP directory for a user registry. The registry is maintained from Access Manager.
2. You've used security Web resources with WebSEAL using LTPA (lightweight third-party authentication). WebSEAL sits at the front of the application server and takes care of the authentication on behalf of the application server. This scenario illustrates how to use LTPA to pass the authentication information to the server.
3. In a solution similar to the previous one, you've had WebSEAL perform the authentication, with the system using TAI (trust association interceptor) to propagate the user information from the security reverse-proxy server to the application server.

You should now have a better idea of how to use Tivoli Access Manager to add security features to your own WebSphere applications.

8 of 10 | Previous | Next

Comments

Back to top

Table of contents

• Before you start
• Installation and configuration
• Tivoli Access Manager scenarios with WebSphere
• Sharing a user registry
• Using WebSEAL to protect Web resources
• Using LTPA to integrate WebSphere and WebSEAL
• Using TAI to integrate WebSphere and WebSEAL
• Summary
• Resources
• About the author

---

8 of 10 | Previous | Next

Next steps from IBM

• Try: Tivoli Access Manager Enterprise Single Sign-on
• Demo: Demo: Tivoli Access Manager for Enterprise Single Sign-On solution overview
• Briefing: Introduction to Tivoli service management environment
• Buy: Tivoli Access Manager Enterprise Single Sign-on

Dig deeper into Tivoli on developerWorks

Try IBM PureSystems. No charge.

Experience today!

---

Get started with the cloud-based trial and pattern development kit.