Share OID for OAM and for Siteminder

Question

Hello,
Has anyone deployed or know if the same OID deployment can be used for OIM-OAM and for policy store of Siteminder? OIM-OAM will have its own user and policies stored in OID, while Siteminder would have its own policy store in the same OID deployment.
If possible, what are the challenges/disadvantages you see/have faced?
Thanks.

Answer 1

Ninad,
It appears you answered your own question. If product A is certified for a certain version of OID and product B is not yet certified, then you would have to wait to upgrade until both are certified if you want to stay within the support policies for both product A and B. That's the major constraint.
As Sagar noted, the policy stores for both OAM (10g) and SiteMinder can be separated into their own directory instances, so they can be tuned separately. OAM 11g no longer stores policy data inteh directory, so it's a non-issue for that product, anyway. However,you will have to apply each products' user schemas to all your users so they can work with either product. Here are the possible issues:
- Your directory server will have to index both OAM and SiteMinder attributes, so it has to index a lot of stuff, which is potentially a lot of overhead for the directory to maintain.
- Each product maintains separate attributes for password policies, so if you enforce password policies using both products, you could run into problems and confusion for your end users.
I'm just wondering why you aren't using one Access Mgmt product for everything? Are you trying to transition from SiteMinder to OAM or something?