BrowserTab with iOS 12


For a project I have to implement a particular authentication system.

The authentication mechanism uses several external sites. Here is the sequence of screens:

    1. My application launches the Safari browser to initialize the connection on our oAuth2 server;
    1. then it is redirected to a site ( to authenticate the Belgian citizen, it is offers different possibility of authentication (via Belgian identity card or via an application " It’sMe ")
    1. the chosen citizen “it’sme (” which opens automatically on his iPhone and the citizen enters his pin code;
    1. the application “itsme” reopens Safari to complete the authentication on the site “csam” then redirects to our server oAuth2;
    1. our servers oAuth2 redirects to the URL “customMyApp://” with an authorization code to reopen the application which ends the authentication in exchange for the authorization code against a Token.

But Apple refuses because “We noticed that the user is taken to Safari to sign in or register for an account, which provides a poor user experience.”

I tried using Safari View Controlle with the BrowserTab plugin but since iOS Safari View Controlle and Safari do not share their session cookies.

We use oAuth2 authentication with the Authorization code flow. If we use the Safari View Controller API for step 1 and 2 when “itsme” opens Safari in step 4 the session is lost because the sessions between Safari View Controller API and Safari aren’t shared.

I tried to update the BrowserTab plugin with SFAuthenticationSession. (Https://

But SFAuthenticationSession is deprecated ( And it did not work.

I have not tried with ASWebAuthenticationSession ( because I saw that all cookies, except session cookies, can be shared with Safari.

Do you have an idea to share a session between Safari View Controller and Safari browser? I can’t find any solution :frowning:

Thanks you

1 Like

Hi FiReBlUe,

Did you manage to find a solution to your problem?
We are currently in the exact same case. We are using ItsMe in our app and it has been refused by Apple because of a “poor user experience” and they ask us to use the Safari View Controller. We’ve tried this solution and it looks like we have the same issues as you.

We would be very glad to know that this problem can ben solved.