We are trying to research different ways of implementing Single sign on in different iOS apps built for our enterprise. App receives cookies and tokens for authentication and authorization when ever a user logs in to one of the apps used in the enterprise. When user opens one of our other enterprise apps, it would be ideal if we could use the cookies and tokens received at the previous app login.
Currently, we are thinking about one of the following options
1 Using ‘App Groups’ feature and store cookies and tokens in shared group container.
2 Use Custom URL schemes to pass around cookies and tokens needed.
Please suggest any other better ways and which one of the above choices would you choose and why…?
@chaitu05 Do you still have issues with this?
Haven’t got many recommendations. Based on research so far, we are trying 1) App Groups for iOS single sign on implementation.
We can close the topic now.
there are 4 answers:
Work with OAuth 2.0
Apply token-based authentication with OpenID Connect and NAPPS
Extend beyond SSO
OpenID is a way to resolve the single-site restriction imposed by OAuth 2.0. As with OAuth, OpenID is supported by all leading authentication providers, such as Microsoft, Google, Facebook, and Twitter. OpenID allows one set of user credentials to access multiple sites. For instance, a Google ID and password can be used to access all of Google’s services. Similarly, a company can use OpenID with OAuth 2.0 to connect a user account from the web, desktop, or mobile to all services using the same authentication. This can include custom solutions, APIs, Office 365, and other third-party, off-the-shelf-solutions.
This topic was automatically closed after 166 days. New replies are no longer allowed.