Learn about UEM / MDM configurations to deploy Enpass

The Enpass app can be deployed on employee’s devices using your UEM (Unified Endpoint Management) or MDM (Mobile Device Management) tool. Enpass supports the following app-configuration keys:

  • policy-email: An email ID that is pre-populated inside the app for activation. This will be a dynamic variable automatically mapped to a user’s email address.
  • policy-enforced: Set this ‘’true’ to ensure that your organization policies are enforced from the beginning. This will enforce the Enpass app activation and policy enforcement with the key ‘policy-email'. Users will not be able to use Enpass without the activation process.

This is how your app configurations for some operating systems should look:

You need to add appropriate registry keys for the user before deploying Enpass. Here is how a .reg file will look.

 

Windows Registry Editor Version 5.00

  

[HKEY_CURRENT_USER\SOFTWARE\Sinew Software Systems Pvt Ltd\Policy]

"policy-email"="user@your-org.io"

"policy-enforced"="true"

Download custom configuration file for macOS from here .

Replace the values of "policy-email" and "policy-enforced" keys appropriately.

Deploy App Config from your MDM. The app config xml will look like:

 

<?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>

You will need to set "policy-email" and "policy-enforced" configuration keys to appropriate values.

Read more about...

Provisioning users with Azure Active Directory