Last updated on JANUARY 08, 2017
Applies to:Oracle Mobile and Social - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
On : Oracle Mobile and Social version 184.108.40.206.0:
We are using Mobile and Social for authenticate native applications in Android and iOS.
The problem is: every login from the app (even with the same cellphone and user) are creating a new device in OAAM.
With the Max Sessions set to 1 in OAM, it prevents the user from having more than one session in OAM at a time. Each subsequent session will invalidate any previous browser session. This works fine.
However, when you integrate OAAM with OAM using the TAP scheme, it works unless you areusing a OAMMS app created with the OAMMS SDK
In this case, With the mobile app, your previous OAM session is invalidate as expected, but you are not challenged.
This does not apply to using browsers within the mobile device. Mobilebrowser sessions used on Mobile devices will properly invalidate previous sessions. It only happens when you use a iOS Mobile app built with a OAMMS SDK which also includes OAAM TAP scheme integration. If OAAM is not in the picture. The issue does not happen.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms