Using Web Services and SOAP API

Natively Integrating with Oracle Adaptive Access Manager 2-3 Figure 2–1 Client Application Using Web Services and Server API

2.1.2 Using Static Linking

Java applications can be static-linked. This scenario only involves local API calls and therefore no remote server risk engine calls SOAP calls. The integration imbeds the processing engine for Oracle Adaptive Access Manager with the application and enables it to leverage the underlying database directly for processing. In this scenario, the application must include the server JARs and configured properties, as appropriate. Even though static linking may provide slightly better performance, it is not suitable for all Java clients. Static linking is recommended for clients developing their own applications with Oracle Adaptive Access Manager built in their J2EE or application. Static-linking an application has several advantages: ■ The application makes no SOAP calls, thus eliminating the need to create and delete TCPIP connections. ■ It experiences no network latencies. ■ It does not require a load balancer.

2.2 Integration Options

This section describes the following integration options: ■ Integrating with Virtual Authentication Devices and Knowledge-Based Authentication ■ Integrating with Knowledge-Based Authentication

2.2.1 Integrating with Virtual Authentication Devices and Knowledge-Based Authentication

This integration consolidates virtual authentication devices and knowledge-based authentication. Globalized virtual authentication device image files including registration flows must be developed by the deployment team. 2-4 Oracle Fusion Middleware Developers Guide for Oracle Adaptive Access Manager Figure 2–2 illustrates an authentication flow example that uses these three solutions virtual authentication devices, knowledge-based authentication, One-Time Password. Note that the flow illustrated is an example and that other authentication flows are possible. The details of the stages in the Figure 2–2 are explained in the following sections: ■ User Name Page S1 ■ Device Fingerprint Flow F1 ■ Run Pre-Authentication Rules R1 ■ Run Virtual Authentication Device Rules R2 ■ Decode Virtual Authentication Device Input P4 ■ Validate User and Password CP1 ■ Run Post-Authentication Rules R3 ■ Check Registration for User C2 ■ Run Registration Required Rules R4 ■ Enter Registration Flow P6 ■ Run Challenge Rules R5 ■ Run Authentication Rules R6 ■ Challenge the User S6 ■ Check Answers to Challenge C3 ■ Lock Out Page S2 ■ Landing or Splash Page S3