The Samsung Enterprise Alliance Program (SEAP) provides SDKs that give you access to proprietary features on Samsung devices. With these features, you can create richer, more secure and differentiated solutions. To develop and commercialize these solutions with our SDKs, you need license keys.

Should a license get into the wrong hands or become compromised, we can revoke it, and deny access to the licensed features.

License types

There are several license types, which provide access to different SDKs and services:

  • Enterprise (ELM) license – Provides access to SDKs meant to be used by larger enterprise partners. These include the Knox Standard, Knox Premium, Knox Customization, and Samsung EDU SDKs.
  • Independent Software Vendor (ISV) license – Provides access to SDKs that anyone can use, like Knox ISV and India Identity.
  • Knox (KLM) license – Provides access to premium features like a Knox container created using the Knox Premium SDK, or devices configured using the Knox Customization SDK. Developers creating an app that use these premium features can get a free development KLM license to test the features. B2B partners integrating the app into their solutions would purchase a production KLM license for each customer, then track and bill their usage of these features.
  • REST API license – Provides web access to the Cloud SDK and web services such as Attestation and Enterprise FOTA.
  • Samsung Knox (SKL) license (beta) – This new entitlement-based license replaces the existing ELM, ISV, and KLM license keys. SKL is a single license key which can be used with any Knox SDK. With the current Beta release, you can use the Samsung Knox License only with the Android version of the Knox Standard SDK. For more about this license type, see License Enhancements.

License verification

Your app provides a license for verification purposes. When using a:

  • Device-based SDK – Your app activates a license before calling APIs in the SDK. A Samsung licensing agent on the device verifies with a web-based license server that you are allowed to use the called APIs. Furthermore, it verifies that the app that is activating the license was the same app that was registered with the license when you first requested the license through the SEAP website.
  • Associate license key – Associate the package name and public key hash with your license key to prevent other unauthorized apps from using it. Upload your package on the Generate License keys page to automatically extract the name and public key hash.
  • Web service – This includes the Cloud SDK, Attestation, and E-FOTA. Your web script includes the license with every REST API call. The web server verifies that you are allowed to use the called REST APIs.

License life cycle

There are two versions of a license:

  • Development – While you are still working on your app, you use a Development license key, which has an expiration date and can be used on a limited number of devices.
  • Production – When you are ready to release your app commercially, you use a Production license key. For:
    • Enterprise (ELM), ISV, Samsung Knox License – If you are registered as a Developer, request an upgrade to Partner status to access production licenses. You can then get the production keys through this SEAP website.
    • Knox (KLM) license – Because these are paid licenses, they are purchased through the Global Samsung Business Network (GSBN). Typically, partners such as MDM vendors and Systems Integrators order production Knox licenses on behalf of their customers through Knox resellers.

For details about the how long you can use these keys and on how many devices, see the tables below.


License keys required by SDK/development tool

KEY TYPE SDK
Standard*, EDU, SDK Premium, UCM, Customization SDK Cloud SDK Enterprise FOTA ISV SDK India Identity SDK Knox Enabled App
Attestation SDP
REST API Key
Identify developer to web servers
         
ELM, ISV Key
Identify developer to device SDKs
   
KLM Key
Track premium features activated (paid) by users
         
SKL Key (beta)
Identify developer, track premium features
             

* The Standard and Customization SDKs include both the Android and Tizen versions. SKL Key is currently used with the Android Standard SDK only.



License keys for developers
SDK KEY TYPE ELM LICENSE KLM LICENSE SKL LICENSE (beta)
Seats Valid for Licenses Seats Valid for Licenses Seats Valid for Licenses
Knox Premium SDK
Knox Customization SDK
Knox Tizen SDK for Wearables
(KLM needed only if using Customization)
Development 10 3 months 1 10 3 months 1
Knox Standard SDK Development 10 3 months 1 10 3 months 1
Knox ISV SDK
Samsung EDU SDK
Knox Tizen SDK for Mobile
Development 10 3 months 1
License keys for partners
SDK KEY TYPE ELM LICENSE KLM LICENSE SKL LICENSE (beta)
Seats Valid for Licenses Seats Valid for Licenses Seats Valid for Licenses
Knox Premium SDK Development 10 6 months 1 10 6 months 1
Production unlimited up to 100 Purchase through Knox reseller
Knox Customization SDK Development 10 6 months 1 30 3 months 1
Production unlimited up to 100 Purchase through Knox reseller
Knox Standard SDK Development 10 6 months 1 10 6 months 1
Production unlimited up to 100 unlimited up to 100
Knox ISV SDK
Samsung EDU SDK
Knox Tizen SDK for Mobile
Knox Tizen SDK for Wearables*
Development 10 6 months 1
Production unlimited up to 100
* Purchase through Knox reseller
Knox Enabled App Development 10 6 months 1
Production

For more information


Contact us if you have any questions.

Join the Samsung Enterprise Alliance Program today to develop and distribute your B2B solution, and connect with the global Samsung community.

Learn more about the program