Proposals Required to Replace Oracle SSO 10g in 11g Environment
We are currently using the Oracle 10g App Server single sign-on component to authenticate users to our "portal" with an external / internet client (sounds like online banking, I think).
SSO uses Oracle Internet Directory to store data, and we could use PL / SQL and Java to access and modify the data stored in the OID (e.g. create / delete users, change / check passwords, etc.)
With the arrival of 11g, Oracle seems to have an orphaned SSO ... it is available, but only as an add-on, and it seems to have been superseded by Oracle Access Manager. My guess is that it will be reset together at 12 g. Also, it is quite difficult to install and work correctly.
So, I am wondering if anyone has experience with the same migration problem as we do? If so, what did you do?
Alternatively, does anyone have any experience of doing something like this using Oracle Access Manager? Do you think he will do what we want?
Or is there a better road to go down? Is there anything else I should consider?
Sorry for the very broad question, but this is one of those situations where a person's experience of doing + not working can make a huge difference for us to make some progress in a timely manner. Thanks.
a source to share
As far as I know, Oracle Internet Directory (OID) is an LDAP compliant directory whereas Oracle Access Manager (OAM) is much more complex and consists of two main systems:
- Identification system (users, groups, workflows)
- Access system (single / multiple domains) SSO solution for Web and non-Web based applications).
Access Manager uses Identity Server, which is a stand-alone server process that communicates with any directory server (AD, OID, Sun Directory server ..).
This way you can use the new OAM and link it to the existing OID ... to retrieve users / groups and metadata. Anything you could do with OIDs would be doable with OAM as it adds more layers of abstraction.
But in my opinion, and considering your case, direct access to LDAP servers (OIDs, AD, etc.) and using lightweight and "home" SSO is cheaper than relying on these big systems .... I think OAM is a useful solution when you have many heterogeneous applications (web, non-web, mobile, ...) and / or multiple organizations / domains with links and / or you need a very scalable approach.
a source to share