Access Manager provides a framework which contains a set of static HTML pages displayed to the user. These default pages can be customized to reflect your company’s look and feel, or replaced entirely with new pages. You can design, implement, and deploy a custom HTML page that, for example, displays a different version of the login form depending on whether the user is accessing via a mobile browser or a desktop browser.
Login, logout, error and password pages are packaged as part of the custom pages framework. An out-of-the-box Web application archive (WAR) file is provided that can be used as a starting point to develop customized pages. This WAR is named oamcustompages.war and located in the MW_HOME/oam/server/tools/custompages/ directory.
In this post I have explained different approach that works in my scenario. When Configured the access manager with application as Single Sign on user will get the default login page of OAM as below once user hit the protected resource.
If Administrator want custom page instead of this default page appearing download the below sample html page and follow the configuration.
1- Download the sample login page and unzip it into web server e.g. OHS httpd docs directory.
2- Edit the auth.html page under jsohs folder. Check for below line
<form id=”loginData” action=”http://<LOAD BALANCER HOST>/oam/server/auth_cred_submit” method=”post” name=”loginData”>
change the <load balancer host> with entry mentioned in oam server host section under configuration as shown below. Copy paste this jsohs folder under httdocs of OHS so that login page is publicly accessible.
4- Change the Authentication Module as below
6- Make sure Web server e.g. ohs directory i.e. jsohs & /oam/** is configured as excluded resource so that webgate will not check for authentication.
Try to access the application you will get custom page.
Next I will try to cover handling the error code which is OAM capturing from LDAP.
Thanks for reading.
Blog About Oracle Technologies 