Greg Hata
Apr 12, 2018
5:16 pm

Unable to acquire MDM_HW_Control

I'm unable to get some of the demo programs to work, specifically knox-sdk-backwards-compatibility and sSDK_Demo_2.  I can successfully activate device admin and activate the license keys for both, but can't, for example, toggle camera permissions for either.  I assume this is likely due to this:
Not granting permission android.permission.sec.MDM_HW_CONTROL to package com.samsung.business.sdk.standard.demo1 (protectionLevel=2 flags=0x3808be44)

I can't acquire any android.permission.sec.* or com.samsung.android.knox.permission.* permissions at all, in fact.  Am I missing a step?

Similar topics

No similar topics found.
Greg Hata
Apr 12, 2018
7:34 pm

Oddly, requesting any such permissions in my AndroidManifest.xml also prevents the sample apps from being granted unrelated permissions, such as Manifest.permission.READ_CONTACTS, as well(though the sample applications will be granted the READ_CONTACTS permission if the .sec and .knox permission requests are commented out or removed from the AndroidManifest.xml file).

Samuel Goldwax
Apr 12, 2018
8:42 pm

Hi Greg,

These sorts of permissions exceptions usually occur when a Knox API is called without a properly activated license key. The two sample apps you've tried actually use two different types of license keys. The backwards-compatibility app uses the new SKL key, while the sSDK_Demo_2 app uses legacy license keys. Which type of license key are you using to activate these sample apps?

Thanks,

Sam

Greg Hata
Apr 13, 2018
2:45 pm

Hey Sam, thanks for responding.  The backwards-compatibility app has options for both types of keys and while I can successfully activate either one, I still can't obtain the necessary permissions.  For the sSDK_Demo_2 app I use the backwards-compatible key(which I assume is the same thing as the ELM key?) and I get the same result - no permissions.

Samuel Goldwax
Selected Answer
Apr 13, 2018
4:42 pm

Hi Greg,

So it sounds like you generated and SKL key for the Knox SDK, which comes with a backward-compatible key. For the backwards-compatibility app, you must activate both licenses for the Knox API call to work properly. The SKL key provided grants all the permissions needed for Knox functionality, however on devices running Knox 2.7.1 or older also requrie the backwards-compatible key to be activated. As for the sSDK_Demo_2 app, the backwards-compatible key provided with the Knox SDK licenses is not the same as a legacy ELM key as no permissions are granted with this license. You'll have to generate a legacy ELM key for this sample app. Let me know if you have any more questions about licensing.

Thanks,

Sam

Comments

Okay, that seemed to work(though it turned out I was also incorrectly requesting the permissions, as well).  Thank you for all your help!

Greg HataApr 17, 2018 at 2:43 pm