UserPassword S1 Stages Integrating with Knowledge-Based Authentication

2-18 Oracle Fusion Middleware Developers Guide for Oracle Adaptive Access Manager this page; however, the post from this page should display a transient intermediate refresh page.

2.2.2.2 Stages

For information on the other stages, see the following sections: ■ Section 2.2.1.2, Device Fingerprint Flow F1 ■ Section 2.2.1.6, Validate User and Password CP1 ■ Section 2.2.1.6.1, Update Authentication Status P5 ■ Section 2.2.1.6.2, Password Status C1 ■ Section 2.2.1.7, Run Post-Authentication Rules R3 ■ Section 2.2.1.8, Check Registration for User C2 ■ Section 2.2.1.9, Run Registration Required Rules R4 ■ Section 2.2.1.13, Challenge the User S6 ■ Section 2.2.1.15, Lock Out Page S2 ■ Section 2.2.1.16, Landing or Splash Page S3 Figure 2–7 Knowledge-Based Authentication Scenario Natively Integrating with Oracle Adaptive Access Manager 2-19 2-20 Oracle Fusion Middleware Developers Guide for Oracle Adaptive Access Manager 3 Integrating Native .NET Applications 3-1 3 Integrating Native .NET Applications This chapter provides details how ASP.NET applications can integrate with Oracle Adaptive Access Manager using the .NET API provided by Oracle Adaptive Access Manager. Descriptions are also provided on the sample applications used to illustrate the integration of different OAAM features with a basic Web application. This chapter contains the following sections: ■ Introduction ■ Oracle Adaptive Access Manager .NET SDK ■ Configuration Properties ■ Oracle Adaptive Access Manager API Usage ■ Integration Example Using Sample Applications

3.1 Introduction

ASP.NET is a web application framework that allows programmers to build dynamic Web sites, web applications and web services. ASP.NET applications, written in any ASP.NET language, can use the OAAM .NET API to call Oracle Adaptive Access Manager. This API communicates with the OAAM server using Simple Object Access Protocol SOAP, as illustrated in Figure 3–1 . Figure 3–1 .NET Application 3-2 Oracle Fusion Middleware Developers Guide for Oracle Adaptive Access Manager

3.2 Oracle Adaptive Access Manager .NET SDK

The Oracle Adaptive Access Manager .NET development kit SDK is packaged in the ZIP file, oaam_native_dot_net.zip in ORACLE_HOMEoaamoaam_ libsdotNet. Sample .NET applications that enable OAAM features require 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: oaam_native_dot_net.zip could be obtained from {ORACLE_ HOME}oaamdistoaam_dist_finaloracle.oaam.libsdotNet.

3.3 Configuration Properties

The Oracle Adaptive Access Manager .NET SDK includes property files that specify values for configuration used by the Oracle Adaptive Access Manager API. A developer can modify these properties to specify application-specific values or add new ones.

3.3.1 How the API Uses Properties

The Oracle Adaptive Access Manager .NET API uses these properties to read configurable values at runtime, such as the location of images for virtual authentication devices. Virtual authentication devices are controls for user input and provide virtual keyboard and personalization. Properties are read and cached from a list of files at startup and updated whenever one of the properties files is updated. The sequence in which the properties files are loaded by Oracle Adaptive Access Manager .NET API is as follows: 1. The lookup.properties file, if present, is loaded first. 2. If the properties.filelist property is defined in lookup.properties, then all the files listed in that property are added to the queue in the listed order. 3. The bharosa_lookup.properties file, if present, is loaded. 4. If the properties.filelist property is defined in bharosa_ lookup.properties, then all the files listed in that property are added to the queue in the listed order 5. All files in the queue are loaded. 6. When any of the loaded properties files is changed, the properties are reloaded. The properties files, including lookup.properties, are searched in the following directories in the order stated in Table 3–1 ; the search for a given file stops when the file is first found or when no file is found. Table 3–1 .NET Property Files Directory Example ApplicationDirectory c:InetpubwwwrootMyApp CallingAssemblyDirectory c:WindowsSystem32 CurrentAssemblyDirectory c:InetpubwwwrootMyAppbin CurrentAssemblyDirectory.. c:InetpubwwwrootMyApp