After upgrading from JDeveloper 18.104.22.168.0 to 22.214.171.124.0 ADF Mobile applications allow to press login twice if connection is slow.
(Doc ID 1624500.1)
Last updated on MARCH 03, 2021
Applies to:Oracle JDeveloper - Version 126.96.36.199.0 to 188.8.131.52.0 [Release Oracle11g]
Information in this document applies to any platform.
After upgrading from ADF Mobile 184.108.40.206.39.62.94 (JDeveloper 220.127.116.11.0) to ADF Mobile 18.104.22.168.39.64.51 (JDeveloper 22.214.171.124.0) we see that sometimes following error is raised on the SOA server:
OWSM Policy Fault : FailedAuthentication : The security token cannot be authenticated
for requests coming in from the ADF Mobile applications. Under normal load it works fine however when a user presses the login button twice on the device then a SOAP request is sent with a header that does not contain a username and/or password. As a security policy has been defined that those values must be present the error is raised. This used to work in 126.96.36.199 where upon pressing login a spinning wheel was shown avoiding the user to click the login button twice. As of 188.8.131.52 this spinning wheel does not appear and thus it is possible to press the button twice causing an invalid request to be sent.
Upgrade from ADF Mobile 184.108.40.206.39.62.94 (JDeveloper 220.127.116.11.0) to ADF Mobile 18.104.22.168.39.64.51 (JDeveloper 22.214.171.124.0)
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