ASP.NET Applications Integration Example Using Sample Applications

Integrating Native .NET Applications 3-11

3.5.2 Sample Application Details

Details about the four applications are provided in this section.

3.5.2.1 SampleWebApp

This application contains the following pages that demonstrate a web application before OAAM integration. 1. LoginPage.aspx ■ Collects the user name and password using a simple HTML form. ■ Validates the login and password information ■ Depending upon the validation result, the user will be redirected to either Success.aspx or to LoginPage.aspx with appropriate error message 2. Success.aspx ■ Displays Successfully logged in message with a link for logout 3. LogoutPage.aspx ■ Logs out the user session and redirects to login page

3.5.2.2 SampleWebAppTracker

This application contains the following pages that demonstrate integration of OAAM tracker functionality to the sample application listed above. This application requires the integration of the OAAM .NET APIs found in the SDK package oaam_native_dot_net.zip. The content of the archive needs to be extracted to the root directory of the web application. 1. LoginPage.aspx ■ Collects the username and password using simple HTML form ■ Saves the login and password in the session ■ Redirects the user to LoginJumpPage.aspx to collect the flash finger print of the user device 2. LoginJumpPage.aspx ■ Loads the user from ARM Adaptive Risk Manager by calling AppUtil.InitUser AppUtil is included in the SDK package. If the user is not found, a new user record will be created Table 3–2 ASP.NET Applications Application Name Description SampleWebApp This is a basic ASP.NET application without OAAM integration. This application is provided so that the reader can easily see incremental changes required to integrate various OAAM feature, such as, tracker, authenticator, and KBA. SampleWebAppTracker This application demonstrates integration of OAAM tracker functionality to SampleWebApp listed above. SampleWebAppAuthTracker This application demonstrates integration of OAAM tracker and authenticator functionalities to SampleWebApp listed above. SampleKBATracker This application demonstrates integration of OAAM tracker and KBA functionalities to SampleWebApp listed above. 3-12 Oracle Fusion Middleware Developers Guide for Oracle Adaptive Access Manager ■ Returns HTML to load flash object bharosa_webflashbharosa.swf in the browser. The flash object calls CookieManager.aspx included in the SDK package with flash finger print details. CookieManager.aspx records the finger print in ARM and in return sets a flash cookie on the users device ■ After a brief wait to allow time to get the flash cookie from ARM, redirects the browser to LoginHandlerPage.aspx 3. LoginHandlerPage.aspx ■ Records the user login attempt with ARM by calling AppUtil.InitTracker ■ Validates the login and password information ■ Updates ARM with the password validation status successwrong userwrong passworddisabled user, etc by calling AppUtil.UpdateAuthStatus ■ If password validation succeeds, runs post-authentication rules by calling AppUtil.RunPostAuthRules ■ If the post-authentication rules return block, blocks the user login after updating ARM with this information ■ Depending upon the validation result andor the rules result, redirects the user to either Success.aspx or to LoginPage.aspx with appropriate error message 4. Success Page ■ Displays Successfully logged in message with a link for logout 5. Logout Page ■ Logs out the user session and redirects to login page

3.5.2.3 SampleWebAppAuthTracker

This application contains the following pages that demonstrate integration of OAAM authenticator and tracker functionalities to the sample application listed above. This application collects the password using authenticators offered by OAAM. This application requires the integration of the OAAM .NET APIs found in the SDK package oaam_native_dot_net.zip. The content of the archive needs to be extracted to the root directory of the web application. 1. LoginPage.aspx ■ Collects the username using simple HTML form ■ Saves the login in the session ■ Redirects the user to LoginJumpPage.aspx to collect the flash finger print of the user device 2. LoginJumpPage.aspx ■ Loads the user from ARM Adaptive Risk Manager by calling AppUtil.InitUser AppUtil is included in the SDK package. If the user is not found, a new user record will be created ■ Returns HTML to load flash object bharosa_webflashbharosa.swf in the browser. The flash object calls CookieManager.aspx included in the SDK package with flash finger print details. CookieManager.aspx records the finger print in ARM and in return sets a flash cookie on the users device