RADIANTONE DEPLOYMENT GUIDE: IBM Tivoli Access Manager
IBM Tivoli Access Manager (TAM) software is designed to work within intranets, extranets, portals and exchange infrastructures. However, consolidating existing user repositories into a single LDAP directory for easy and cost effective deployment can be an integration challenge. This problem can be addressed by using RadiantOne to federate multiple user data stores and making them appear as one logical directory for TAM.
This integration guides documents how to use the RadiantOne Identity and Context Virtualization Platform to:
- Reduce integration cost and deployment time of IBM Tivoli Access Manager (TAM) by leveraging existing data stores instead of having to replicate and synchronize user information into a single user directory.
- Eliminate risk associated with code modifications to TAM required to access multiple authentication and authorization sources.
- Simplify complex authentication schemes in TAM deployment and increase the flexibility of your infrastructure by providing a dynamic directory service that can adapt to a changing business climate.
RadiantOne Deployment Guide for IBM Tivoli Access Manager
TABLE OF CONTENTS
- ARCHITECTURE OVERVIEW
- SOLUTION DESCRIPTION
- TAM INSTALLATION STEPS
- RADIANTONE CONFIGURATION STEPS
- SETTING UP THE VDS AS THE REGISTRY SERVER
- CONFIGURING RADIANTONE TO CONNECT/AGGREGATE EXISTING USER REPOSITORIES
- DEPLOYMENT SCENARIO
- IMPORTING USERS FROM MULTIPLE SOURCES INTO THE TAM REGISTRY
- CREATING USER ACCOUNTS FROM TAM
- VALIDATING USER ACCOUNTS
- DELEGATED AUTHENTICATION
- DEFINING GROUPS
- SETTING ACL
- PROTECTING RESOURCES
|