Error: "URL Security cannot be asserted." returned from login step in correlated Oracle Applications R12 script
The default correlation performed by VuGen may not select the correct value for the "oas" parameter and consequently the login step fails during replay. The recommended correlation to perform is detailed herein.
Having correlated a Web Protocol script recorded against an Oracle Applications R12 application, the login step continues to fail and the following message:
URL Security cannot be asserted. The given URL has either expired or has been tampered with. Please contact your System Administrator for help.
is displayed in the page returned by the server.
This message indicates that a correlated value in the URL sent to the server during script replay is not correct. This is due to an incorrect correlation.
Typically the login step is performed by a "POST" action such as:
If an incorrect correlation of the value of the "oas" parameter is performed, this login step will fail.
Typically there may be several different values for the "oas" parameter present in data returned by the server to the client during recording of the business process. The value that is required for this parameter for the login step is returned by the server within the following content:
Action.c(nnn): ethod="POST" action="/OA_HTML/OA.jsp?page=/oracle/apps/fnd/sso/login/webui/MainLoginPG&_ri
and therefore the correlation statement that is required should be similar to: