Can you describe the use case a little further? The user is inside the native app, and then clicks a button and gets kicked out to a mobile web app? Typically in OpenID Connect, the session is stored in the browser. So if the person opens up a number of Google chrome browsers, they should have a session across all. But if they were to open two separate browsers, like Chrome and Mozilla, they would have to authenticate in both browsers. If its using the system browser, then they should get SSO across both apps. But if it's closer to the second scenario, the user would need to authenticate again in the new browser. Thanks, Will

We have a situation where we'd be in a native iPhone or Android app and we would link over to a web page that requires authentication with our SSO provider (OpenID Connect/Gluu) outside of the native app in their mobile browser. We want to know if the authentication session would persist where they wouldn't have to re login. Let me know if I'm still not explaining this correctly.

So if the user already has a session in the web browser they are kicked out too, e.g. Safari or Chrome, then they wouldn't have to login again. If they do not already have a session in that browser, they would be required to login. All other apps leveraging that browser would inherit the SSO session. Does that help clarify?

Yep, I think that clarifies. Thanks!