Detection Matching For Web Applications.
(Doc ID 549756.1)
Last updated on MARCH 05, 2019
Applies to:Oracle Enterprise Single Sign-On Suite Plus - Version 10.1.4.1 and later
Information in this document applies to any platform.
***Checked for relevance on 05-MAR-2019***
To describe how to handle the most common scenarios where detection matching needs to be used when creating web application templates in Oracle Enterprise Single Sign-On (eSSO)
When a web page is loaded in Internet Explorer (IE) or a Mozilla based browser, the first matching criteria used by the eSSO agent is the URL. If the URL matches with the one specified in the web application template, eSSO will start processing the additional matching rules, if any are present.
If all rules are processed successfully, the agent will inject the credentials into the web page controls, as defined by the application template.
Usually, after the process is completed and the page is submitted, the URL of the next page will be different. However, there are some applications which will return to the same page and the same URL adding just a response message or disabling a button. This will cause the eSSO agent to inject the credentials again. To avoid this behavior, additional detection matching rules can be added in the application template to stop it recognizing the second page.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|1. The Second Page contains a message in addition to the First Page|
|2. The Second Page contains an attribute on one of the tags|