VRM or CRM - You Decide
By Mark Wilcox - OVD Product Manager on Apr 09, 2009
Eve Maler (btw who pronounces her last name differently than Sophia Maler who is our PM for federation. I suspect but have not yet confirmed that any female involved with SAML must have the last name of "Maler" but I digress) recently wrote up her ideas on a new protocol "ProtectServe". In particular to enable a new type of experience around "relationship management" (which sounds like an episode of Oprah about marriage but again I digress).
Which from the best I can figure involves some-type of automation to help manage what data is sent automatically on your behalf to different entities.
And it also relates to the concept of "Vendor Relationship Management" aka VRM.
Now, I happen to be at Oracle aka home of Siebel and related CRM products. Now, I don't know if we have an official position on VRM and if we do, what it is. If I find out, I'll share.
But until then, it occurred to me - we actually could support this type of scenario today. And with some of the Social CRM projects they have cooking - could possibly do more in the future.
However, here is how the scenario could be worked out today.
- The RM sends us some data via SAML (whether this is a traditional IDP or InfoCard)
- Java application gets the SAML data and converts into a Java object
- Java application then makes a call to Siebel's Web Service APIs (either directory or via an Application Integration Architecture pack)
Today there would be lots of protocol translations and related activities but our future plan is that ArisID Beans (part of the IGF implementation) would allow us to simplify the programming model. But that will have to wait for a future post.