Back to top

Universal Credential Management

Last updated July 26th, 2023

KSP provides a group of policies to manage universal authentication credentials in both external and internal device storage, for example, a smartcard, micro SD card, or embedded Secure Element. Depending upon your network and security needs, you can enable or disable UCM policies as well as configure advanced settings for your UCM plugins.

Before you can enable UCM plugins for your devices, you must create and configure at least one UCM configuration policy.

1. Create UCM configuration policy

The following example describes the process to create a new UCM configuration policy, called Screen lock, that dictates how the UCM plugin restricts access to specific apps on the target device when the device is locked.

  1. In your UEM console, open the Device Configuration Profile that is associated with your target devices > click the appropriate option to edit the profile.

  2. On the policy settings homepage, next to UCM plugin configurations, click Configure. The page refreshes to show the UCM plugin configurations menu item on the left hand navigation menu.

  3. On the refreshed navigation menu, click UCM plugin configurations > Add setting. The UCM plugin configuration page opens to show a set of fields that help you create and customize your UCM plugin.

  4. On the UCM plugin configuration page, do as follows:

    1. In the Name of UCM plugin configuration field, enter Screen lock.


      Always choose a name that highlights the main feature or use of the UCM plugin configuration that you are setting up. You can then reference this name in KSP to apply these settings to the target device.

    2. In the Package name of UCM plugin application field, enter the package name for your UCM vendor’s application. Sample format is com.mycompany.ucm.plugin. Refer to the UCM vendor application’s Google Play Store page for the correct package name.

    3. In the Credential usage list, select Screen lock.

    4. If your UCM vendor’s plugin supports PIN caching, in the Pin properties area > in the PIN timeout type list > select Same as screen lock. The UCM plugin now requires re-authentication whenever the screen locks.

    5. In the Application access controls area > Type of access restrictions list > select Unrestricted access.

    6. In the Access control when device or workspace is locked area > Lock credential storage when device or workspace is locked list > click True.

    7. In the List of apps allowed to access credential storage when locked field, enter the package names — in a comma-separated list — to allow specific apps to access UCM credential storage when the device is locked.

    8. List of certificates to install on this credential storage after configuration.

  5. Click OK to save this new UCM configuration. This UCM configuration restricts all apps’ access to UCM credential storage, with the exception of specific apps, when the device is locked.


    Repeat steps 1 to 5 for each type of UCM configuration policy you want to create in your Device Configuration Profile.

2. Use an existing UCM configuration policy

The following example shows you how to use the Screen lock UCM configuration policy that you created earlier to automatically secure target devices in the High security devices device group when the screen is locked.

  1. After you’ve created the Screen lock UCM configuration policy in your chosen Device Configuration Policy, go to Groups > All groups.

  2. On the All groups page, confirm that the High security devices device group exists. Refer to your UEM console’s help documentation for information on creating a new or editing an existing device group.

  3. Go to the Device Configuration Policy that contains the Screen lock UCM configuration policy > click Assignments > Include tab.

  4. On the Include page, in the Assign to list, select High security devices > click Save.

  5. Depending upon the settings you’ve chosen for deploying Device Configuration Policy changes, the new UCM Configuration Policy is deployed on the devices in the High security devices group.

Is this page helpful?