erbr.blogg.se

Ensure that all your applications use the same Client ID or Application ID.

To enable SSO across your applications, you'll need to do the following steps, which are explained in more detail below: MSAL supports SSO sharing through iOS keychain access groups. See SSO between ADAL and MSAL apps on macOS and iOS for instructions for cross-app SSO between ADAL and MSAL-based apps.

The apps must be distributed by the same Apple Developer. MSAL Objective-C support migration and SSO with ADAL Objective-C-based apps. Silent SSO between ADAL and MSAL macOS/iOS apps.MSAL on macOS only supports WKWebView which doesn't have SSO support with Safari. This type of SSO is currently not available on macOS. To learn more about the web views that MSAL supports, visit Customize browsers and WebViews.

If you use the default web view in your app to sign in users, you'll get automatic SSO between MSAL-based applications and Safari. It's not limited to apps distributed by the same Apple Developer, but it requires some user interaction. It uses existing sign-in state from other apps and the Safari browser. SSO is achieved through the ASWebAuthenticationSession class. This type of SSO requires a broker application be installed on the user's device. Microsoft provides apps called brokers that enable SSO between applications from different vendors as long as the mobile device is registered with Azure Active Directory (Azure AD). It provides silent SSO (that is, the user isn't prompted for credentials) by reading refresh tokens written by other apps from the keychain, and exchanging them for access tokens silently. This type of SSO works between multiple apps distributed by the same Apple Developer. This article covers the following SSO scenarios: The Microsoft Authentication Library (MSAL) for macOS and iOS supports single sign-on (SSO) between macOS/iOS apps and browsers.