Entries Tagged 'Use Case' ↓

Aside manageability and robustness, companies are buying an LDAP server for its performance. A directory server traditionally is used as a centralized lookup service, or an identity backbone. With the recent release, we are now marrying the performance of commercial LDAP server with the versatility of a virtual directory by way of persistent cache feature. The basic concept of persistent cache is quite simple. By storing the cached entries in a disk-based mechanism, those entries will survive a sudden-loss of power (recycle). Since we can store those entries on any LDAP or database servers, it also gains an unlimited storage capacity.

(Illustration diagrams)

UPDATED: A complete documentation and etrust module JAR file is now online.

Penrose can leverage Sun Java Directory Server to store its persistent cache. Here is the HOW-TO.

Penrose supports Mult-target Writeback where a single LDAP operation against Penrose server would be translated to many write operations to the backend stores (multitarget). If all back-end stores are XA-aware, Penrose can execute XA-write back (for example, System 1 and System 2 must update, or the entire transaction rolls back). This feature is quite useful for provisioning multiple accounts.

Most of user identities information are not stored in directory. They are stored in a database, a flat-file, or within legacy application. Virtual Directory is one of the newest invention which can help enterprise to expose and repurpose those identities. The process to make those identities available in a standard Directory Access Protocol (LDAP) is very straightforward. All you need to do is to use a mapping tool, commonly provided by Virtual Directory technology, to create a “pointer” from your existing user identities to your “virtual” Directory Information Tree.

You can check-out a flash demo here.