Hi, I would like to check if passing the session information from the mobile app to the target page when opening the page using the InAppBrowser Open action is possible. If I am already logged in to the same domain of the mobile app if I open another web page of the same domain using the InAppBrowser, the web page shouldn't prompt me for another login (Single Sign On concept).
I have tested, and the only approach that achieves this is by setting the Target of the Open Client Action to SYSTEM. The other options - IN APP BROWSER and IN APP SYSTEM BROWSER do not work.
Mobile App
Target = IN APP BROWSER, Sign on is prompt again
Target = SYSTEM, no need to sign in again. This is the correct destination.
Hey Kyle,
Just so that we have more information about it, how are you treating the "Options" property of the client action? Are you using the default values?
Thanks.
I'm looking into this as well as it relates to SSO. Both iOS and Android have changed their support for inapp browsing to use the SFWebController and Chrome Custom Tabs. Both of these support sessions and full cookie jar access where as the WebView does not. The InApp plugin from Cordova only supports the WebView and not the new tools for inapp browsing. My question, is there any plans to move to the new inapp browsing instead of the legacy methods. By doing so, this would enable enterprises the ability to handle SSO correctly. Right now, you can send the user to login, but they have to always enter the userid and password because the cookie jar is not available. This is a very bad experience for Enterprise users.