Query and Parse. com | Springer. Link. You're seeing our new chapter page and we'd like your opinion, send feedback. Microsoft Intune App SDK for i. OS developer guide. The Microsoft Intune App SDK for i. OS lets you incorporate Intune app protection policies (also known as APP or MAM policies) into your native i. To run: require libcurl-dev or libcurl-devel(on rpm linux based) $ git clone https://github.com/CoolerVoid/0d1n/ need libcurl to run $ sudo apt-get install libcurl-dev. Introduction This document summarizes changes made in all the 1.5.0 update releases, including a link to the original 1.5.0 release notes. Note that bug fixes in.
OS app. A MAM- enabled application is one that is integrated with the Intune App SDK. IT administrators can deploy app protection policies to your mobile app when Intune actively manages the app. Prerequisites. You will need a Mac OS computer that runs OS X 1. Xcode 8 or later installed. Your app must be targeted for i. OS 9 or above. Review the Intune App SDK for i. OS License Terms. Print and retain a copy of the license terms for your records. By downloading and using the Intune App SDK for i. OS, you agree to such license terms. If you do not accept them, do not use the software. Download the files for the Intune App SDK for i. OS on Git. Hub. What’s in the SDKThe Intune App SDK for i. OS includes a static library, resource files, API headers, a debug settings . Mobile apps might simply include the resource files and statically link to the libraries for most policy enforcement. Advanced Intune MAM features are enforced through APIs. This guide covers the use of the following components of the Intune App SDK for i. OS: lib. Intune. MAM. The Intune App SDK static library. If your app does not use extensions, link this library to your project to enable your app for Intune mobile application management. Intune. MAM. framework: The Intune App SDK framework. Link this framework to your project to enable your app for Intune mobile application management. Use the framework instead of the static library if your app uses extensions, so that your project does not create multiple copies of the static library. Intune. MAMResources. A resource bundle that has resources that the SDK relies on. Headers: Exposes the Intune App SDK APIs. If you use an API, you will need to include the header file that contains the API. The following header files include the APIs, data types, and protocols which the Intune App SDK makes available to developers: Intune. MAMApp. Config. h. Intune. MAMApp. Config. Manager. h. Intune. MAMData. Protection. Info. h. Intune. MAMData. Protection. Manager. Intune. MAMDefs. h. Intune. MAMEnrollment. Delegate. h. Intune. MAMEnrollment. Manager. Intune. MAMEnrollment. Status. h. Intune. MAMFile. Protection. Info. h. Intune. MAMFile. Protection. Manager. Intune. MAMLogger. Intune. MAMPolicy. Intune. MAMPolicy. Delegate. h. Intune. MAMPolicy. Manager. Intune. MAMVersion. Info. h. Developers can make the contents of all the above headers available by just importing Intune. MAM. h. How the Intune App SDK works. The objective of the Intune App SDK for i. OS is to add management capabilities to i. OS applications with minimal code changes. The fewer the code changes, the less time to market- -without affecting the consistency and stability of your mobile application. Build the SDK into your mobile app. To enable the Intune App SDK, follow these steps: Option 1 (recommended): Link Intune. MAM. framework to your project. Drag Intune. MAM. Embedded Binaries list of the project target. Note. If you use the framework, you must manually strip out the simulator architectures from the universal framework before you submit your app to the App Store. See Submit your app to the App Store for more details. Option 2: Link to the lib. Intune. MAM. a library. Drag the lib. Intune. MAM. a library to the Linked Frameworks and Libraries list of the project target. Add - force_load {PATH_TO_LIB}/lib. Intune. MAM. a to either of the following, replacing {PATH_TO_LIB} with the Intune App SDK location: The project’s OTHER_LDFLAGS build configuration setting. The UI’s Other Linker Flags. Note. To find PATH_TO_LIB, select the file lib. Intune. MAM. a and choose Get Info from the File menu. Copy and paste the Where information (the path) from the General section of the Info window. Add these i. OS frameworks to the project: Message. UI. framework. Security. Mobile. Core. Services. System. Configuration. Image. IO. framework. Local. Authentication. Audio. Toolbox. framework. Add the Intune. MAMResources. Copy Bundle Resources within Build Phases. If your mobile app defines a main nib or storyboard file in its Info. Main Storyboard or Main Nib field(s). In Info. plist, paste these fields and their corresponding values under a new dictionary named Intune. MAMSettings with the following key names, as applicable: Main. Storyboard. File. Main. Storyboard. File~ipad. Main. Nib. File. Main. Nib. File~ipad. Note. If your mobile app doesn’t define a main nib or storyboard file in its Info. You can view Info. Show Raw Keys/Values. Enable keychain sharing (if it isn't already enabled) by choosing Capabilities in each project target and enabling the Keychain Sharing switch. Keychain sharing is required for you to proceed to the next step. Note. Your provisioning profile needs to support new keychain sharing values. The keychain access groups should support a wildcard character. You can check this by opening the . For example: < key> keychain- access- groups< /key>. YOURBUNDLESEEDID.*< /string>. After you enable keychain sharing, follow these steps to create a separate access group in which the Intune App SDK will store its data. You can create a keychain access group by using the UI or by using the entitlements file. If you are using the UI to create the keychain access group, make sure to follow the steps below: If your mobile app does not have any keychain access groups defined, add the app’s bundle ID as the first group. Add the shared keychain group com. The Intune App SDK uses this access group to store data. Add com. microsoft. Add com. microsoft. If you are using the entitlement file to create the keychain access group, prepend the keychain access group with $(App. Identifier. Prefix) in the entitlement file. For example: * `$(App. Identifier. Prefix)com. App. Identifier. Prefix)com. Note. An entitlements file is an XML file that's unique to your mobile application. It is used to specify special permissions and capabilities in your i. OS app. If the app defines URL schemes in its Info. URL scheme. If the app defines Document types in its Info. Document Content Type UTIs" array, add a duplicate entry for each string with a "com. For mobile apps developed on i. OS 9+, include each protocol that your app passes to UIApplication can. Open. URL in the LSApplication. Queries. Schemes array of your app's Info. Additionally, for each protocol listed, add a new protocol and append it with - intunemam. You must also include http- intunemam, https- intunemam, and ms- outlook- intunemam in the array. If the app has app groups defined in its entitlements, add these groups to the Intune. MAMSettings dictionary under the App. Group. Identifiers key as an array of strings. Configure Azure Active Directory Authentication Library (ADAL)The Intune App SDK uses Azure Active Directory Authentication Library for its authentication and conditional launch scenarios. It also relies on ADAL to register the user identity with the MAM service for management without device enrollment scenarios. Typically, ADAL requires apps to register with Azure Active Directory (AAD) and get a unique ID (Client ID) and other identifiers, to guarantee the security of the tokens granted to the app. Unless otherwise specified, the Intune App SDK uses default registration values when it contacts Azure AD. If your app already uses ADAL to authenticate users, the app must use its existing registration values and override the Intune App SDK default values. This ensures that users are not prompted for authentication twice (once by the Intune App SDK and once by the app). Recommendations. It is recommended that your app links to the latest version of ADAL on its master branch. The Intune App SDK currently uses the broker branch of ADAL to support apps that require conditional access. These apps therefore depend on the Microsoft Authenticator app.) But the SDK is still compatible with the master branch of ADAL. Use the branch that is appropriate for your app. Link to ADAL binaries. Follow the steps below to link your app to the ADAL binaries: Download the Azure Active Directory Authentication Library (ADAL) for Objective- C from Git. Hub, then follow the instructions on how to download ADAL using Git submodules or Cocoa. Pods. Include the ADALi. OSBundle. bundle resource bundle in the project by dragging the resource bundle under Copy Bundle Resources within Build Phases. Add - force_load {PATH_TO_LIB}/lib.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
November 2017
Categories |