This is an archive related to a previous version of Esri Maps for MicroStrategy. If you need the current version go to http://doc.arcgis.com/en/maps-for-microstrategy/.
Your iOS application can use a digital certificate to access resources on ArcGIS for Server that are secured using Public Key Infrastructure (PKI). In such a scenario, each user who is authorized to access the secured resources is provided a digital certificate (also known as a client certificate) that can be used to confirm his or her identity when connecting to the server. This certificate file is in pkcs#12 format and usually has a .p12 or .pfx extension.
To install the certificate on a user’s iOS device so that your app can use it, you must make the certificate available on the user’s device and programmatically import the certificate into the keychain access group of your app.
The Em4Mstr framework provides an API to import the digital certificate into the app. To programmatically import the certificate into the keychain access group of your app, you must make changes in Xcode.
<key>CFBundleDocumentTypes</key> <array> <dict> <key>CFBundleTypeIconFiles</key> <array/> <key>CFBundleTypeName</key> <string>Certificate file</string> <key>CFBundleTypeRole</key> <string>Editor</string> <key>LSHandlerRank</key> <string>Owner</string> <key>LSItemContentTypes</key> <array> <string>com.esri.px12</string> </array> </dict> </array> <key>UTExportedTypeDeclarations</key> <array> <dict> <key>UTTypeConformsTo</key> <array> <string>public.data</string> </array> <key>UTTypeIdentifier</key> <string>com.esri.px12</string> <key>UTTypeTagSpecification</key> <dict> <key>public.filename-extension</key> <array> <string>px12</string> </array> </dict> </dict> </array>
The first step in installing the certificate is to make it available on the user’s device. Before sending the certificate to the user by email attachment, you must change its file extension from .p12 or .pfx. If this is not done, the iOS system will attempt to import the certificate into the default keychain when the user tries to open the attachment. As custom iOS apps do not have access to the default keychain, applying a custom file extension to the certificate is required.
The app now uses this PKI certificate to authenticate with your PKI Portal Server.