Failed To Validate USERTOKEN From Mobile And Social In SSO session via OAG
(Doc ID 2119384.1)
Last updated on OCTOBER 26, 2021
Oracle Mobile and Social - Version 184.108.40.206.0 and later Information in this document applies to any platform.
In an integrated environment of Oracle Identity and Access Management 220.127.116.11 with also SOA protected resources and Oracle API Gateway 18.104.22.168 , the mobile application using OAMMS SDK fails to authenticate
A custom Mobile Application using Oracle Access Management Mobile and Social SDK, the authentication provider attempts to authenticate using the /oamauthentication service provider. With this provider, the application can successfully retrieve the USERTOKEN and ACCESSTOKEN using rest operations. For SOA operations side, an Oracle API Gateway is deployed in front of client to protect and authorize the users to access the resources.
When sending any of these mobile tokens as ssosession http header to the OAG API Gateway to access the SOA operations protected by the API, the OAM response is:
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!