After upgrading from JDeveloper 188.8.131.52.0 to 184.108.40.206.0 ADF Mobile applications allow to press login twice if connection is slow.
Last updated on MARCH 08, 2017
Applies to:Oracle JDeveloper - Version 220.127.116.11.0 to 18.104.22.168.0 [Release Oracle11g]
Information in this document applies to any platform.
After upgrading from ADF Mobile 22.214.171.124.39.62.94 (JDeveloper 126.96.36.199.0) to ADF Mobile 188.8.131.52.39.64.51 (JDeveloper 184.108.40.206.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 220.127.116.11 where upon pressing login a spinning wheel was shown avoiding the user to click the login button twice. As of 18.104.22.168 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 22.214.171.124.39.62.94 (JDeveloper 126.96.36.199.0) to ADF Mobile 188.8.131.52.39.64.51 (JDeveloper 184.108.40.206.0)
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms