Skip to content

Commit 933fa50

Browse files
authored
Merge pull request #7391 from hhawkins/patch-4
Updating the MSAL section
2 parents a454c23 + 6e75371 commit 933fa50

1 file changed

Lines changed: 14 additions & 8 deletions

File tree

memdocs/intune/developer/app-sdk-ios.md

Lines changed: 14 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ keywords:
77
author: Erikre
88
ms.author: erikre
99
manager: dougeby
10-
ms.date: 02/28/2022
10+
ms.date: 05/23/2022
1111
ms.topic: reference
1212
ms.service: microsoft-intune
1313
ms.subservice: developer
@@ -172,26 +172,32 @@ In `- startProvidingItemAtURL:completionHandler:` check if you should encrypt fi
172172

173173
In `- importDocumentAtURL:toParentItemIdentifier:completionHandler:` check whether the file is encrypted using `isFileEncrytped:` API in `IntuneMAMFileProtectionManager`. If it is then decrypt it using `decryptFile:toCopyPath:` API of `IntuneMAMFileProtectionManager`.
174174

175-
## Configure MSAL
175+
## Setup MSAL
176176

177177
The Intune App SDK uses the [Microsoft Authentication Library](https://github.com/AzureAD/microsoft-authentication-library-for-objc) for its authentication and conditional launch scenarios. It also relies on MSAL to register the user identity with the MAM service for management without device enrollment scenarios.
178178

179179
### Set up and configure an AAD app registration
180180
MSAL requires apps to [register](/azure/active-directory/develop/quickstart-register-app) with Azure Active Directory (AAD) and create a unique client ID and redirect URI, to guarantee the security of the tokens granted to the app. If your application already uses MSAL for its own authentication, then there should already be an AAD app registration/client ID/redirect URI associated with the app.
181181

182-
Developers should [grant their new or existing app registration access to the Intune MAM service](../developer/app-sdk-get-started.md#give-your-app-access-to-the-intune-app-protection-service-optional), to ensure the application is able to successfully acquire MAM policies.
182+
If your app does not already use MSAL, you will need to configure an app registration in AAD and specify the client ID and redirect URI that the Intune SDK should use.
183183

184-
### Link to MSAL binaries
184+
If your app currently uses ADAL to authenticate users, see [Migrate applications to MSAL for iOS and macOS](/azure/active-directory/develop/migrate-objc-adal-msal) for more information on migrating your app from ADAL to MSAL.
185185

186186
It is recommended that your app links to the latest release of [MSAL](https://github.com/AzureAD/microsoft-authentication-library-for-objc/releases).
187187

188-
Follow [these instructions](https://github.com/AzureAD/microsoft-authentication-library-for-objc#installation) to link your app to the MSAL binaries.
188+
### Link MSAL to Your Project
189189

190-
1. If your app does not have any keychain access groups defined, add the app's bundle ID as the first group.
190+
Follow the [installation](https://github.com/AzureAD/microsoft-authentication-library-for-objc#installation) section to put the MSAL binaries in your app.
191191

192-
2. Enable MSAL single sign-on (SSO) by adding `com.microsoft.adalcache` to the keychain access groups.
192+
### Configure MSAL
193193

194-
3. In the case you are explicitly setting the MSAL shared cache keychain group, make sure it is set to `<appidprefix>.com.microsoft.adalcache`. MSAL will set this for you unless you override it. If you want to specify a custom keychain group to replace `com.microsoft.adalcache`, specify that in the Info.plist file under IntuneMAMSettings, by using the key `ADALCacheKeychainGroupOverride`.
194+
Follow the [configuration](https://github.com/AzureAD/microsoft-authentication-library-for-objc#configuring-msal) section to configure MSAL. Make sure you follow all the steps in the configuration section. Disregard step one if your app is already registered in AAD.
195+
196+
The points below contain additional information to configure MSAL and link to it. Follow these if they apply to your application.
197+
198+
* If your app does not have any keychain access groups defined, add the app's bundle ID as the first group.
199+
* Enable MSAL single sign-on (SSO) by adding `com.microsoft.adalcache` to the keychain access groups.
200+
* In the case you are explicitly setting the MSAL shared cache keychain group, make sure it is set to `<appidprefix>.com.microsoft.adalcache`. MSAL will set this for you unless you override it. If you want to specify a custom keychain group to replace `com.microsoft.adalcache`, specify that in the Info.plist file under IntuneMAMSettings, by using the key `ADALCacheKeychainGroupOverride`.
195201

196202

197203
### Configure MSAL settings for the Intune App SDK

0 commit comments

Comments
 (0)