Configure Pulse Secure on Android

MobiLock and Android for Work makes it easy for you to configure Pulse Secure VPN on your managed Android devices. Follow the guide below to configure Pulse Secure.

Before you Begin

  1. Complete Android for Work Setup in MobiLock Dashboard.
  2. Enroll your corporate owned devices using afw#mobilock
  3. Invite your Employees to enroll their Personal devices.

The following feature works only for devices enrolled via afw#mobilock and where MobiLock application is set as a Device Owner or employee owned devices where MobiLock creates a Work Profile. It will not work if you are using legacy methods to enroll the devices.

Search and Approve Pulse Secure

The first step is to search and approve Pulse Secure for your organization. The steps are,

  1. Sign In MobiLock Dashboard.
  2. Navigate to Enterprise > My Apps > Play For Work Apps

  3. Click on SEARCH&ADD button to see the Google Play dialog.
  4. In the Google Play dialog search for Pulse Secure,
  5. Click on the Pulse Secure app and select Approve

  6. Follow the onscreen instructions to approve the application. Click Done to close the dialog and now the app starts appearing on the MobiLock Dashboard.

Configuring Pulse Secure Settings

Once you have the Pulse Secure app, the next step is to configure the application. The steps are,

  1. Click on the Pulse Secure application to see the details card.
  2. Click on the App Configurations tab and click CREATE to see the configuration options.
  3. Pulse Secure gives you the following configuration options,

    Connection Name

    The display name for the VPN as shown on user's mobile device

    URL

    The URL of the headend that is the actual Pulse Secure VPN Server.

    Authentication Type

    Choose the authentication type for the VPN connection.

    Username

    The username to be used or blank. You can use custom properties for a dynamic configuration, like $device.<customproperty> or $user.email

    Password

    Optional field to specify the password for the VPN connection.

    Username2

    The alternate username to be used or blank.

    Password2

    The alternate password to be used or blank.

    Certificate Alias

    The Alias of the certificate in Android KeyStore if the Authentication type is certalias.

    VPN Standard

    Enable this setting to make this VPN as the default VPN.

    Realm

    Enter the VPN Realm, that specifies the compliance rules for the users to use the VPN.

    Role

    Define the user roles, that is the capabilities related to access features and other personalization settings.

    Route Type

    Choose if the VPN has to be used at a device level or app level.

    AppVPN Action

    Choose the action for Applications, whether to allow or disallow. Basing on the list of packages in AppVPNPackages will be treated.

    AppVPN Packages

    Comma separated list of packages to be either allowed or disallowed for VPN.

    Always on VPN

    Enable this to use this VPN as an always ON VPN and requires a logoff to disconnect.

    Stealth Mode

    Enable Stealth mode authentication.

  4. Once you have entered the values, click on SAVE to save the configuration. All the saved configuration appear in the list.

Publishing the Application and Configuration

Once you have created the configuration, the next step is to publish the application and then the configuration. The steps are,

  1. From the App Details card, click on the App Information tab and click on PUBLISH

  2. Select the Android Device Groups/Profiles/Devices where you want to publish the application and click PUBLISH

  3. Now click on the App Configuration tab. Click on the Publish icon.
  4. Select the Android Device Groups/Profiles/Devices where you have published the application in Step 3, and click PUBLISH

  5. This will cause the applications to be installed on the devices and then configured based on the configuration.

Please contact your VPN Service provider in case you need details on how to use a particular setting and the accepted values.


How did we do?


Powered by HelpDocs (opens in a new tab)