Introduction
The Knox Service Plugin (KSP) is a solution that enables Enterprise Customers to use Knox Platform for Enterprise features as soon as they are commercially available. This automatic deployment method ensures that IT admins can use the latest Knox features on the day it is launched, instead of waiting for their UEM to specifically integrate the features.
For more information: https://docs.samsungknox.com/knox-service-plugin/admin-guide/welcome.htm
With Workspace ONE UEM 1907 and above you can leverage App Config to configure the KSP when it is pushed as a Public application using App & Books. However, certain use cases may require KSP to be pushed an internally managed application. In such a scenario you will need to push a profile with the XML to configure the KSP application.
Key Considerations
Currently the KSP app config needs to be present on the device before the KSP application is installed. In order to achieve this order of operations leverage product provisioning and create a dependency within the KSP application product to push the app config product first.
The below steps can be used to extract the app config and build the XML for any application
In order to leverage KSP as internally managed application you need to perform the following steps:
Extract the app_restrictions.xml file to get the list of key-value pairs that you will need to build the XML
Build the XML which will be pushed as part of the custom settings profile
Apply the KSP config to the device
Extract the app_restrictions.xml file to get the list of key-value pairs that you will need to build the XML
Download the windows wrapper script (Save Link as apktool.bat) and download the apktool
Copy both the files into a folder (name it APKTool) in C:\Documents
Navigate to Environment Variables (This PC > Properties > Advanced System Settings)
4. Choose the system variable for the JAVA path and click Edit
5. Add a new path which points to folder you created with the APK tool files
6. Run the command apktool d <APK Name> using command prompt
7. The above command will extract the APK files to the Current Location/<APK Name> (C:/KSP). Open the app_restrictions.xml located in C:/<App Name>/res/xml
Build the XML which will be pushed as part of the custom settings profile
8. Create an Android device profile (Devices > Profiles & Resources > Profiles > Add)
9. Add a Custom Settings payload and paste the XML that was built.
10. Save and Publish the profile to be pushed to the assigned devices.