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 or deny access to the licensed features.

License types

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

  • Samsung Knox License (SKL) – Provides access to the new Samsung Knox SDK. This new license replaces the existing ELM, ISV, and KLM license keys using an Android permissions model to identify the features used by an app. For more information about this license type, see License Enhancements. If your app needs to run on a device on Knox 2.7 or earlier, a backwards-compatible key must be used along with the SKL.
  • REST API license – Provides web access to the Cloud SDK and web services such as Attestation and Enterprise FOTA.

The following license types were replaced by the new Samsung Knox license:

  • Enterprise (ELM) license – Provides access to SDKs that require partner authentication for production distribution.
  • Independent Software Vendor (ISV) license – Provides access to SDKs that anyone can use, like the Knox ISV and Samsung India Identity SDKs.
  • Knox (KLM) license – Provides access to features from the Knox Tizen SDK for Wearables and the Knox Cloud SDK. Developers requiring these features can get a free development license for testing purposes. B2B partners integrating the app into their solutions can purchase a production KLM license for each customer and track and bill their usage of these features.

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.
  • 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.
    • Samsung Knox License (SKL) – If you are registered as a Developer, request an upgrade to Partner status. You can then generate a Production key on this website.

      Note: The Production SKL currently only allows access to Knox Standard features in the Knox SDK. In the near future, it will allow access to all features. For the time being, you need to use the ELM and KLM keys if you would like to access premium features.

    • Enterprise License (ELM), Independent Service Vendor license (ISV) – You can contact us to get a Production key.
    • Knox License (KLM) – Contact a Knox reseller to purchase a production key.

See Generate License Keys for more detailed information regarding license permissions.


License keys required by SDK/development tool

Key Type Knox
SDK
UCM
SDK
India Identity
SDK
Edu
SDK
Cloud
SDK
E-FOTA
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 Key1
Identify developer, track premium features
         

1. Must be used with a backwards-compatible key on devices running Knox 2.7 or earlier.



License keys for developers
SDK Type ELM License KLM License SKL License + Backwards Compatible Key
Seats Valid for Licenses Seats Valid for Licenses Seats Valid for Licenses
Knox SDK** Development 1         10 3 months 1
Samsung EDU SDK Development 10 3 months 1        
Knox Tizen SDK for Wearables Development 10 3 months 1 10 3 months 1    
License keys for partners
SDK Type ELM License KLM License SKL License + Backwards Compatible Key
Seats Valid for Licenses Seats Valid for Licenses Seats Valid for Licenses
Knox SDK** Development1         30 6 months 1
Production (SKL)2         unlimited up to 100
Production (ELM)3 unlimited up to 100        
Production (KLM)4     Purchase through Knox reseller    
Samsung EDU SDK Development 10 6 months 1        
Production     up to 100        
Knox Tizen SDK for Wearables* Development 10 6 months 1 30 3months 1    
Production     up to 100 *Purchase through Knox reseller    
Samsung India Identity Development 10 6 months 1        
Production              
** Find more about Knox permissions here.
1. Development key provides all Knox permissions (Standard, Premium and Customization).
2. Production (SKL) key provides Standard permissions only. For paid features, you need Production ELM and KLM keys.
3. Production (ELM) key provides Standard permissions.
4. Production (KLM) key provides Premium and Customization permissions.
5. Samsung Galaxy Tab Iris (Model SM-T1161R) is the only device supporting Samsung India SDK - Knox ver 2.5.1
6. The backwards-compatible key is required on devices running Knox 2.7 or earlier. A single backwards-compatible key works with multiple SKL keys.

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