This page covers how to install Enpass Password Manager on iOS devices, configure it for your organization, and deploy it at scale using a UEM/MDM platform.
Manual Installation
For unmanaged environments or individual installs:
-
Open the Enpass listing on the App Store.
-
Tap Get to download and install.
-
Tap Open to launch the app.
Alternatively, visit enpass.io/downloads and follow the link to the App Store.
Requirements: iOS 15.7 or later. Compatible with iPhone and iPad.
App Configuration
Before deploying Enpass, administrators can pre-configure the application by pushing a managed app config payload from your MDM. This is applied when the app is first launched on the user's device.
The app config payload is an XML plist with the following structure:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"
"http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>policy-enforced</key>
<string>true</string>
<key>policy-email</key>
<string>user@your-org.io</string>
</dict>
</plist>
Replace user@your-org.io with the dynamic variable for the user's email address as defined in your UEM solution.
For a full description of all supported keys, see the App Configuration Keys Reference.
Deploying via UEM/MDM
For managed environments, deployment involves adding Enpass as a managed iOS app and pushing an app configuration policy.
General steps for any UEM/MDM platform:
-
Add Enpass Password Manager as a managed iOS Store app in your UEM. Search for
Enpass Password Managerin the App Store connector within your UEM console. -
Create a managed app configuration and apply the plist payload above, substituting the appropriate dynamic email variable for your platform.
-
Assign both the app and the configuration to the appropriate user or device groups.
-
Ensure the configuration is applied before or at the same time as the app deployment.
Deploying via Microsoft Intune?
For step-by-step instructions specific to Microsoft Intune, including App Store deployment and App Configuration Policy setup, see: