Specifically, the example demonstrates how you can single-sign-on with Okta to a mobile app on one device (such as your iPhone), then have access to all your apps on another desktop device (such as your Mac). We also share an example app to demonstrate how you can use the token-exchange solution to build SSO for your apps, not only within the same device, but also across devices. In this article, we describe the solution and compare it to an existing approach. Okta recently added support for this draft spec. Thus, there is still a dire need for an industry-standard solution.įortunately, this problem is widely recognized, and an OIDC draft spec Native SSO for Mobile Apps has been released to address the issue using a token-exchange approach. To date, complex proprietary solutions have not proven interoperable with the variety of native applications an enterprise installs on employee devices. In comparison with desktop or web apps, it’s even more critical to enable SSO for mobile apps, due to the smaller keyboard and screen on a mobile device, which makes password input more painful. There are also a large number of internal native apps available to employees within an enterprise. In 2020, a report from RiskIQ counted 8.9 million mobile apps.
LOGMEIN DESKTOP APP OKTA HOW TO
This is partly due to the lack of an industry standard or best practice on how to accomplish native SSO.Īlthough there is no standard yet, there’s been growing demand for a solution, due to the continued expansion of native apps, both desktop and mobile. Unfortunately, for desktop and mobile applications (often referred to as “native apps”), the seamless web SSO experience (also referred to as native SSO) has not caught on. When you hear SSO (Single Sign-On), you probably immediately think of web apps, and how you only need to sign into one web app first, then all other web apps give you seamless access.
0 kommentar(er)
