Integration Oracle Access Manager with SharePoint 2013

Requirement

Integration Oracle Access Manager with SharePoint and sync user profiles. Import user’s profiles from Active directory and OAM. The imported profiles should resolve in the people picker. The scope of this development is targeted to SharePoint 2013.

Implementation Options

Integrate OAM with LDAP store

• Enable synchronization of Oracle Identity Manager roles, users, and their hierarchy to an LDAP directory
• Enable Identity Administration Integration with Oracle Access Manager (OAM).
• Synchronize user profiles between the SharePoint Server directory and the Access Manager directory

References:

http://docs.oracle.com/cd/E17904_01/install.1111/e12002/oimscrn006.htm 

http://docs.oracle.com/cd/E27559_01/admin.1112/e27239/oam11_sharepoint2010.htm 

Sync with BCS data

• Integrating Oracle data into SharePoint by creating a connection through the BCS to Oracle database and then use that as a secondary import source for SharePoint
• User Profile Service. SharePoint uses active directory connection as the primary and Business data connection as Secondary Store for user profiles. Import user profiles from Active directory first, import profile properties from BCS External store (Ex. OAM Database), and then create connection of type BCS with one-to-one or one-to-many mapping relationship between imported active directory properties & BCS store.

References:

http://technet.microsoft.com/en-us/library/gg188041.aspx#importBusiness 

http://sharepoint.stackexchange.com/questions/89663/user-profile-multiple-data-sources 

https://pholpar.wordpress.com/2013/08/21/importing-sharepoint-user-profile-properties-using-bcs-net-connectivity-assembly/ 

Implementing a custom claim provider

• Create a claims provider that understands Oracle Access Manager and authorize SharePoint resources.
• When SharePoint gets the request, it will first forward the request to the SharePoint security token service so that it can convert the windows identity to claims identity.
• Custom claims provider could be used to guarantee about the identity in hand and it could look up the user in the Oracle. The custom claims provider will be designed to write into the claim any particular attribute SAML token and send it back to SharePoint.

References:

http://msdn.microsoft.com/en-us/library/office/ff699494(v=office.14).aspx   http://sharepointdragons.com/2012/04/26/claims-in-sharepoint-2010-the-sequel/ 

http://blog.podrezo.com/sharepoint-custom-claims-provider/