OUD comes as a strategic directory services were we are unifying the services under one product.
For proxy-ing into other directories this is handled directly with OUD setup in proxy mode.
You currently need OVD to perform virtual directory capabilities.
Our synchronization tool is indeed DIP that works with OUD and can leverage OUD as the configuration storage for synchronization profiles.
Hope this clarifies.
Feel free to reach me out for more.
Thanks for your reply Etienne.
In view of 'OUD comes as a strategic directory services were we are unifying the services under one product.' and OVD still needed for vistualization , can you please help me understand why we should be pitching clients to use OUD and not OID + OVD ? This is a very common argument , hence.
I do understand that OUD is file-based , quicker , has proxy features , elastic , replication enabled without it needed to be stopped etc.
This was discussed couple times. One of those conversation was:
To make it simple OID leverage an external Oracle DB, while OUD comes with an embedded storage that you don't need to administer.
Glad to follow up further via email if needed.