Let config = MSALPublicClientApplicationConfig(clientId: 'your-client-id',Ĭonfig.cacheConfig. and only shared with other applications declaring the same access group Tokens will be saved into the 'custom-group' access group MSALPublicClientApplicationConfig *config = *application = initWithConfiguration:config error:nil] If you'd like to use a different keychain access group, you can pass your custom group when creating MSALPublicClientApplicationConfig before creating MSALPublicClientApplication, like this: On macOS 10.15 onwards (macOS Catalina), MSAL uses keychain access group attribute to achieve silent SSO, similarly to iOS. However, it behaves similarly from an SSO perspective by ensuring that multiple applications distributed by the same Apple developer can have silent SSO. MSAL on macOS uses access group by default.ĭue to macOS keychain limitations, MSAL's access group doesn't directly translate to the keychain access group attribute (see kSecAttrAccessGroup) on macOS 10.14 and earlier. On iOS, add the keychain group to your app's entitlement in XCode under Project settings > Capabilities > Keychain sharing.

Alternately, press the reset button to reset it. This ensures the best SSO experience between multiple apps from the same publisher. How to Fix could not sign in to iMessage or Facetime: Update macOS, Set Correct Date & Time, Reset NVRAM, Modify Keychain Access Settings. MSAL on iOS uses the access group by default. This article covers how to configure app entitlements so that MSAL can write cached tokens to iOS and macOS keychain.

For more information, see Apple's Keychain Items documentation. SSO is achieved via the keychain access groups functionality. Caching tokens in the keychain allows MSAL to provide silent single sign-on (SSO) between multiple apps that are distributed by the same Apple developer. When the Microsoft Authentication Library for iOS and macOS (MSAL) signs in a user, or refreshes a token, it tries to cache tokens in the keychain.

Reset keychain