I 'm evaluating using Auth0 as an SSO back-end and I can’t seem to find a clear answer on whether and how to support both iOS (and Android - but testing on iOS) and web clients.
- I created an SSO service and iOS client following the Quickstart and login and retention of session state worked fine
- I then followed the Vanilla JS Quickstart to see how it was configured – and then updated both the JS client configs and the Native SSO service to support the web client
- I can login in to either but…
- …the web client is ‘aware’ of logins / logouts from itself or the iOS client but…
- the iOS client is not receiving session updates or able to use SSO coming from the web…
- Basically it works from Web to iOS but not the other way…
Actually, I may have that backwards. When I login on the Web and close my iOS app (default client example) and then “login” again on iOS – it gets the session from the server and bypasses the login form. When I do the reverse, login on iOS and then refresh the web client (also the default example app) and login, I get the login form and not session redirection…
I’ve seen a lot of mention of “universal login” in the forums but that’s not a thing / term of art on iOS so saying “use universal login” doesn’t mean anything to me.
I have configured my iOS app to allow me to choose either the default WebAuth, WebAuth with an ephemeral session, and the safariProvider and none work to provide the expected SSO experience on iOS. Of course, I don’t expect ephemeral session or external Safari to work in this scenario but only mention it to show I’ve tried 3 of the 4 supported flavors. (I haven’t yet implemented a pure native / basic auth example because I want to see the browser based flow working before expending the additional effort.)
Is what I’m trying to do possible with Auth0?
If so, what am I doing wrong?
If so, can you update your docs to show an example of a ‘mixed’ SSO service as I suspect the majority of SSO customers are looking for this solution.
Thanks for any guidance you can provide!
Tim