Oracle Virtual Directory Presentations at Oracle OpenWorld 2008
By Mark Wilcox - CTO - Oracle Consulting Security-Oracle on Aug 24, 2008
OOW is coming up and of course I will be there. Besides being able to find me at our booth, I will also be presenting at the conference.
This year I will be presenting at the main conference with one of our customers - The State of Delaware.
The presentation is:
Session ID: S298925
Session Title: Using Oracle Virtual Directory to Integrate Microsoft Active Directory, Oracle Database, and Oracle Applications
Track: Identity Management
Room: Golden Gate C3
Start Time: 13:00
The State of Delaware will be going over their implementation of OVD with PeopleSoft. And I will be providing the general overview of OVD & identity virtualization.
I am also planning on presenting at the Unconference. I say planning because unlike the traditional OOW conference, nobody knows who is going to present or when until each morning when people post the topics & get slotted. I think it's useful for getting topics posted that are emerging or emerge during the conference itself that otherwise wouldn't have a forum. It is however, slightly confusing to the uninitiated since I had to spend a day with management last week explaining to them that I couldn't guarantee when or where my Unconference presentation would be delivered :).
The Unconference presentation will most likely be our first demonstration of our "Identity Beans" API. Identity Beans is our current internal name for our implementation of the IGF Attribute Services API. I wouldn't say "internal name" to mean "code name". Rather a reflection of the need for a less wordy name for "IGF Attribute Services API" which the IGF team also recognized. I had dinner with Prateek Mishra last week and we bounced around a couple of other ideas including perhaps having one name for the Oracle Java implementation and another for the API specification.
The quick summary on Identity Beans is that this an API that we believe will make it simpler to use identity attributes. Barring some unforeseen issue this is the API that Fusion application security will use to access the identity information exposed by Fusion applications (such as HR ) and automatically linked with the enterprise directory (in most cases we assume this will be AD).
This is the API that will generate CARML mapping files - though we will likely ship with a set of pre-defined mapping for Fusion apps data. And while it does generate CARML (or can generate it's code from a CARML file) - the goal is that this is like the XML mapping files in Hibernate or Toplink - there for application consumption only. Nobody should ever see (or edit by hand) XML in our GA release.
I will be blogging more about "Identity Beans" over the next few months which will show how this makes secure identity development quicker and easier.