In this 5-minute tech tip video, We are going to look at Oracle Access Manager (OAM) Architecture.
Oracle Access Manager is a part of Oracle Identity & Access Manager Suite and a recommended Single Sign-on (SSO) solution for Web Applications .
As shown in Video, Oracle Access Manager (OAM) is consists of .
- Application Tier: In this tier, you have OAM and the Application that you want to protect via OAM. Oracle Access Manager is deployed on a Weblogic Domain. The domain consists of an Admin Server and Managed Server. On Admin Server, you have Access Manager Console deployed that is a Graphical User Interface (GUI) to manage Oracle Access Manager. OAM Managed Server is where actual authentication and SSO happens.
- DB tier: In this tier, you have Database and LDAP Server. The database is used to store metadata and all the policies which are nothing but the rules governing how a particular URL is protected. Then you have User data store which is LDAP Server something similar to Microsoft Active Directory (AD) or Oracle Internet Directory (OID) or Oracle Unified Directory (OUD) or third party LDAP server. In this LDAP server, you store Users and groups.
- Web Tier: In this tier, you have the web server. You put a web server in front of the application that you want to protect via OAM. On this Web Server, you put a policy enforcement point or a gatekeeper or Policy Enforcement Point (PEP) called Webgate.
Any request that comes to the webserver, the Webgate will collect the URL, take it to the OAM and ask OAM what login page user should be redirected to. Then OAM will submit collected userid/password to the LDAP Server (OID/OUD or AD). LDAP server will validate the username and password and on successful authentication, a session will be created in OAM. Then OAM will return to the
LDAP server will validate the username and password and on successful authentication, a session will be created in OAM. Then OAM will return request back to the web Server with an authenticated user ID. The WebServer will forward that request to the application with authenticated user id and the application will create its own session related to that user. After that application can be accessed by the user as long as SSO cookie is valid or someone has not terminated User session from Oracle Access Manager or the user has not Logged out from the application itself.
So this is all in nutshell about Oracle Access Manager Architecture.
We Cover this in Detail in our Oracle Access Manager & Oracle Identity Manager Administration Training also we cover Architecture, Install, Configure, Integrate, HA, DR, Troubleshooting etc in training.
- Oracle Identity & Access Management (OAM/OID) 12c/11g Click here
- Oracle Access Manager (OAM/SSO) Training : Step by Step Activity Guides /Hands-On Lab Exercise Click here
- Oracle Access Manager 12c (22.214.171.124.0): Download & Installation: Part I Click Here
- Oracle Access Manager 12C: RCU & Configure Domain (126.96.36.199.0) [Part2] Click Here
- Overview of Oracle Identity & Access Management Products (OAM, OIM, OID, OUD, OES, OIF….) Click Here
- Documentation & Download of Oracle IDM 12cPS3 here
- IDM 12cPS3 installation and Configuration here.
- Download IDM Software and create Schema click here
- Console in OAM: OAM Console, WebLogic & EM
- OID Consoles Overview: ODSM, Weblogic & EM
Next Task For You
Join our free live webinar to polish your learnings and basics for IDAM.
Did You Find this Video useful?
What more topics you want to see as part of 5 Minute Tech Tips on Oracle Access Manager?
Leave a Comment.