In this scenario, the application communicates with Oracle Adaptive Access Manager using the Oracle Adaptive Access Manager native client API (SOAP service wrapper API) or via Web services. Customers implementing a native integration should develop their own application using the sample application as a reference only. For example, the sample application does not have proper error handling it only provides basic elements of API usage. The example application is available as a form of documentation to illustrate how to call the product APIs. ![]() Integrating with Knowledge-Based Authentication Integrating with Virtual Authentication Devices and Knowledge-Based Authentication The integration options are presented in the following sections: Within these flow sections, there are details about which API should be called at each stage. The typical process flows for the authentication and challenge scenarios are presented in this chapter. This chapter contains guidelines to integrate a client application with Oracle Adaptive Access Manager using the APIs the server exposes. ![]() ![]() Using the Oracle Adaptive Access Manager APIs, you can:Ĭhange the default user registration flowĬontrol and manage the authentication process flow The application invokes Oracle Adaptive Access Manager directly and the application itself manages the authentication and challenge flows. Native Oracle Adaptive Access Manager integration involves customizing your application to include OAAM API calls at various stages of the login process. Oracle Adaptive Access Manager provides APIs to fingerprint devices, collect authentication and transaction logs, run security rules, challenge the user to answer pre-registered questions correctly, and generate virtual authentication devices such as KeyPad, TextPad, or QuestionPad. 2 Natively Integrating with Oracle Adaptive Access Manager
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |