Knox Tizen SDK frequently asked questions

We now provide the Knox SDK on the Tizen platform, with additional SDKs planned.

The Knox Tizen SDK for Wearables is currently supported on: Galaxy Watch, Galaxy Watch Active, Galaxy Watch Active 2, Gear S2, Gear S3, and Gear Sports wearable devices.

You must install Tizen SDK - Wearable 2.3.1 version.

For more information, refer to the installation section in Samsung Knox Tizen SDK for Wearables Developer Guide.

You must install the following extension SDKs:

• Samsung Certificate Extension SDK
• Samsung Wearable Extension SDK

There are two modes in which you can use Samsung wearable devices:

• Companion mode — When a Samsung wearable device without the need of an additional SIM card is paired with a Galaxy smartphone via Bluetooth, the wearable is in companion mode. In this mode, by using the wearable management app on the smartphone, you can send and receive SMS, calls, emails, and push notifications from the Samsung smartphone to the Samsung wearable.
• Standalone mode — When a Samsung wearable device has a separate SIM card, and is paired with a Galaxy smartphone via Bluetooth, the wearable is in standalone mode. In this mode, you can directly make and receive calls, SMS and email directly from your wearable. You can also forward voice calls from your phone to the wearable device number and using the wearable management app on the you can forward notifications from the Samsung smartphone to wearable.

Currently, the supported Wi-Fi security types are:

• OPEN
• WEP
• WPA-PSK
• WPA2-PSK
• EAP-PEAP
• EAP-TLS
• EAP-TTLS
• EAP-SIM
• EAP-AKA

You can use the API method knox_attestation_get_attestation_blob (const unsigned char *nonce, int size, unsigned char **blob_data, int *blob_data_size) to get the blob data to check if the device is available for authentication.

A nonce is a random number that uniquely identifies each attestation request. The server creates and returns a nonce, which you use to identify an attestation request. Each nonce is valid for a short time period, after which the Attestation Server fails any request made using that nonce. This is to avoid a replay attack that could allow an attacker to reuse a past attestation result.

ProKiosk mode enables system integrators to restrict/limit the functionality of the Samsung wearable device to a single app. Refer to the ProKiosk API here.

To use the Knox Tizen SDK for Wearables APIs, you require the Knox Platform for Enterprise (KPE) license key. For more information, see About licenses.

If you have existing ELM and KLM keys, you can continue using them. However, you cannot generate new ones. Below is a chart of the legacy licenses used for different API categories:

Yes. You need to associate your Tizen app on Knox Partner Program if you are using the Knox Tizen SDK for Wearables commercially.

If your app is in development and not yet ready for commercial release, you do not need to associate it with your KPE Development key.

You can call the API method knox_custom_deregister_client (const char *pkg_name) to de-register the client app.

Please note that the policies set by the client app will remain as is even if the app is de-registered. That is, there will be no change in the state of the Samsung wearable device.