Specifying Credentials to the Oracle Adaptive Access Manager SOAP Server

3-10 Oracle Fusion Middleware Developers Guide for Oracle Adaptive Access Manager add key=BharosaSOAPPassword value=soapUserPassword add key=BharosaSOAPDomain value=soapUserDomain appSettings ■ By adding the following properties to one of the application properties files: BharosaSOAPUser=soapUser BharosaSOAPPassword=soapUserPassword BharosaSOAPDomain=soapUserDomain

3.4.8 Tracing Messages

The Oracle Adaptive Access Manager .NET API allows to print trace messages of various levels using diagnostics switches in web.config. The trace messages can be saved to a file by configuring the appropriate listeners. The following web.config file sample shows the configuration of switches and a listener that writes trace messages to a file: system.diagnostics switches add name=debug value=0 add name=info value=0 add name=soap value=0 add name=perf value=0 add name=warning value=1 add name=error value=1 add name=traceTimestamp value=1 add name=traceThreadId value=1 switches trace autoflush=true indentsize=2 listeners add name=BharosaTraceListener type=System.Diagnostics.TextWriterTraceListener, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089 initializeData=BharosaTrace.log listeners trace system.diagnostics

3.5 Integration Example Using Sample Applications

This section shows you how to integrate an application through using one of the sample applications provided in the SDK.

3.5.1 ASP.NET Applications

The following four ASP.NET applications are included in this sample package to demonstrate integration of various OAAM 11g features in ASP.NET based applications. Note: When specifying SOAP credentials in this way, you can use either clear text or an encrypted string for a value typically, for the value of a password 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.