Dashboard > Penrose > Use Cases > CA eTrust Directory
Penrose
CA eTrust Directory
Added by Jim Yang, last edited by Jim Yang on Apr 27, 2006  (view change)
Labels: 
(None)


Overview

Companies can use their existing CA eTrust directory as a future-proof identity backbone by leveraging Penrose virtual directory. In the diagram below, Penrose can use CA eTrust directory to store its cached entries. The cache entries will be made available to eTrust Directory. User and application can then query CA eTrust directory and leverage its high-speed and replication feature.

Modification to CA eTrust DS will be propagated to Legacy Data Store

Modification to Legacy Data Store will be propagated to CA eTrust DS

Setup Instructions

The followings are the instructions on how to setup eTrust Directory and Penrose to run the example included in Penrose.

  1. Install eTrust Directory
  2. Install MySQL
  3. Install Penrose
  4. Configure eTrust Directory
  5. Configure MySQL
  6. Configure Penrose

Test Cases

The followings are several scenarios for testing the eTrust Directory integration:

  1. Updating Datasource
  2. Updating eTrust Directory

References

Children   Hide Children | View in hierarchy
eTrust Directory Integration - eTrust Directory Configuration (Penrose)
eTrust Directory Integration - eTrust Directory Installation (Penrose)
eTrust Directory Integration - MySQL Configuration (Penrose)
eTrust Directory Integration - MySQL Installation (Penrose)
eTrust Directory Integration - Penrose Configuration (Penrose)
eTrust Directory Integration - Penrose Installation (Penrose)
eTrust Directory Integration - Updating Datasource (Penrose)
eTrust Directory Integration - Updating eTrust Directory (Penrose)

Site running on a free Atlassian Confluence Open Source Project License granted to Safehaus. Evaluate Confluence today.
Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.5.4 Build:#809 Jun 12, 2007) - Bug/feature request - Contact Administrators