RADIANTONE DEPLOYMENT GUIDE: Oracle Access Manager

Oracle Access Manager (OAM) combined with RadiantOne VDS becomes one of the most flexible Identity and Access Management Solutions on the market today.

This integration guide documents how to use the RadiantOne Identity and Context Virtualization Platform to overcome known major limitations in OAM:

1. Protect RDBMS tables: OAM is not able to manage or enforce access control on application which have a user base in RDBMS tables.  Most organization have user data in one or more databases.  For example, most popular CRM tools store customer information in RDBMS tables and applications are authenticating customers by querying these databases. 
   
   
2. Integrate and Manage Multiple User Stores: In most scenarios, a single user directory cannot meet all identity requirements of an organization.  OAM provides disjoint search functionality to manage multiple user directories using a single Identity system.  The limitation of this approach is that it requires a separate Identity System admin to manage each user and separate workflow configuration for each directory server. 
   
   
3. Unify Split User Profiles: RadiantOne’s integration layer publishes, in real-time, composite user profiles from multiple disparate security systems into a single common namespace, providing the most up-to-date and accurate identity information possible.
   

• Overview
  
  • Features
    
  • Architecture
  • Components
    
• Limitations and Solutions
  
• Product Configuration
  
  • Update Schema in all Underlying Stores
    
  • Extract schema from User Data Stores
    
  • Map Object and Attributes to a Common Format
    
  • Build Virtual Directory Trees
  • Build a Common Namespace
    
  • Configure a User Directory for OAM based on RadiantOne VDS