Originally, we issued two types of licenses, Enterprise (ELM) licenses to access our enterprise-grade SDKs and Knox (KLM) licenses to access our premium SDK features. These legacy licenses came with a fixed set of API methods that you could call. Since Knox 3.0, we have introduced a new license key type called the Knox Platform for Enterprise (KPE) license. Three license keys fall under the KPE license type – the KPE Development license, the KPE Standard license, and the KPE Premium license, which will be available later this year.

KPE licenses allow you to access several different permissions using a single licensing model, which simplifies the license activation progress. To enhance security and avoid misuse of your Knox Platform for Enterprise (KPE) license, you can also register your app while requesting the Knox Platform for Enterprise (KPE) license to certify your ownership over it. Registered app information is verified during the license activation process, allowing us to ensure your keys are not used to distribute malicious apps.

This license model provides the following benefits:

  • Better security - You need to register information about the app that will use the new Knox Platform for Enterprise (KPE) license. Only the registered apps will be able to activate the new Knox Platform for Enterprise (KPE) license.
  • Flexible permissions declaration - You can select only the permissions you want to use by declaring them in your app's AndroidManifest.xml. This approach is aligned with Google’s method for declaring permissions.
  • Single convenient license key model - You can now activate one license key type and access multiple permission groups.

The KPE licenses allow you to access permissions and API methods from the Knox SDK. In the near future, they will also allow you to access permissions and API methods from the Knox Tizen SDK for Wearables.


Enroll to generate license key

How it works

    1. Get development license key - Through this SEAP portal, you can get a KPE Development license key for development purposes. For security purposes, you can identify the apps that will use this key by providing their app package name and public key hash. To do this, you either upload the app (and let the SEAP Portal extract the package name and hash) or manually enter the information yourself.
    2. Grant key - The SEAP Portal requests a license from the Samsung License Server, then displays your license through your SEAP license dashboard.
    3. Declare the permissions & activate the license - Declare the permissions used by your app in its Android Manifest file. In the app, activate your Development license by calling the API method KnoxEnterpriseLicenseManager.activateLicense.
    4. Validate License - What happens next depends on the device and the Knox Platform version it is using:
      • Knox v3.0 or later - A License Agent on the device sends your KPE license request to the Samsung License Server, asking for the permission declared in the Android manifest file.
      • Knox v2.8 or later - A License Agent on the device sends your KPE license request to the Samsung License Server, asking for permission predefined in the license key.
      • Knox v2.7 or earlier - You activate both the KPE license as well as a backwards-compatible key, which has no permissions but is needed to trigger a request for Knox Platform for Enterprise (KPE) license permissions.

    The Samsung License Server ensures the app activating a license has been registered, determines what permissions that license has, and sends this information to the License Agent on the device. Your app can now execute the API methods that it was granted permission to use.

    1. Get commercial license key - When you are ready to release your app, you need a commercial KPE license. How you get one depends on whether your app uses:
      • Standard Knox permissions only - Get a KPE Standard license through the SEAP portal.
      • Premium or Customization Knox permissions - An authorized Knox reseller or EMM vendor provides commercial licenses to enterprises using the app. Each license activation is tracked and billed. Commercial ELM and KLM licenses are still currently used for paid features, but a commercial KPE license will soon replace them.

    You can continue to use legacy ELM and KLM keys that are already issued. We will eventually stop issuing the legacy ELM and KLM keys and instead provide only KPE licenses with a backwards-compatible key.

    Next steps

    Back to About License keys