Ever stepped into Identity Management and been hit by a wave of confusing acronyms—OID, OVD, OUD, ODSEE—wondering, "They all handle directories, but what's the real divider here?" Plenty of us have been right there with you.
What is a Directory Service?
A directory service acts as a centralized, hierarchical database that stores and organizes information about network resources like users, groups, devices, printers, and applications, mapping names to attributes such as usernames, passwords, roles, and access permissions. It enables authentication, authorization, and resource location via protocols like LDAP, functioning like a networked phonebook for admins and apps to query and manage identities efficiently.
As of today ORACLE has 4 directory services:
OID (Oracle Internet Directory) excels as Oracle-native LDAP storage built on Oracle Database, perfect for Fusion Apps and WebLogic authentication with tight 19c integration and multi-master replication.
OUD (Oracle Unified Directory) serves as the modern all-in-one solution—storage, proxy, and virtualization in Java-based architecture that scales elastically for cloud/AD hybrids and Kubernetes deployments.
OVD (Oracle Virtual Directory) specializes in virtualization, joining disparate LDAP, DB, and REST sources into a unified view without data replication—ideal for silo consolidation. ODSEE (Directory Server Enterprise Edition) delivers high-scale storage and proxying with carrier-grade reliability, best for legacy Sun DS migrations and bi-directional AD password sync.
Below are the key features of each directory service.
Oracle Internet Directory (OID)
Built completely by Oracle from scratch.
Needs Oracle Enterprise Edition database to store all the data.
Oracle keeps fixing security issues and improving it because some Oracle apps still need it.
Oracle Directory Server Enterprise Edition (ODSEE)
Started as Sun's LDAP server, famous for handling huge company and telecom setups.
Has its own built-in database to store user info.
Comes with a separate replication server to copy data between ODSEE servers.
Now in "maintenance only" mode - still supported but no new features coming.
Oracle Unified Directory (OUD)
Newest Oracle directory, based on Sun's OpenDS tech.
100% Java - super easy to run anywhere, deploy, and update.
Uses lightweight Berkeley database that's fast and tough for storing data.
Can also work as a replication server or proxy for balancing load/sharing data.
Oracle's #1 choice for all new projects and setups.
Oracle Virtual Directory (OVD)
No built-in storage - it doesn't save data itself.
Runs as a separate Java process, not inside WebLogic.
Acts like a "virtual LDAP mirror" - connects underneath to AD, OID, OUD, ODSEE, or even databases using special adapters to pull and mix data on the fly.
native storage, OUD for modern scalability, OVD for virtualization, and ODSEE for legacy high-scale ops.
rget specific identity needs: OID for Oracle-
When to Choose What?
OID: Deep Oracle integrations (Fusion, 19c auditing)
OUD: New projects, cloud/hybrid, future-proof
OVD: Mix multiple directories without copying data
ODSEE: Legacy Sun migrations, heavy AD sync needs
Comments
Post a Comment