...
The app config contains the following parameters:
- customerIdjoinToken: The value in the XML file.
- groupName: In the Cloud Services Portal, the name of the group to which the endpoint is to be moved. If the name is not present in the Cloud Services Portal, then add it to the All BloxOne Endpoints group before installing the app-config file.
- userId: The unique name that identifies the mobile device. The configured name is displayed in the Cloud Services Portal, on the Manage > Endpoints page.
- allowServiceControl: By default, this value will be True. To disallow and hide service control, use the toggle switch to change this value to False.
...
6. The app config with the editable groupName and userId attribute fields should appear:
| Note | ||
|---|---|---|
| ||
BloxOne EP version iOS 2.0.7 and above uses joinToken instead of customerId for authorization, for existing devices with older version of the app the update to latest version is automatic, for fresh installation on new devices the joinToken should be updated in the configuration settings. |
Image 9
7. Click Next to continue to the iOS Distribution screen.
...
13. Open the BloxOne EP app on your device; on Android devices, find the app in the Work Profile. If prompted, accept the DNS Proxy acknowledgement. After a moment, the app will be in a protected state:
Image 15
Step 6: Add an App Config for the BloxOne Android app
...
4. Click Next to continue to the Configuration screen.
5. Add the config file previously downloaded from the Cloud Services Portal.
6. The app config with the editable groupName and userId attribute fields should appear.
| Note | ||
|---|---|---|
| ||
BloxOne EP Android version 1.0.9 and below require the customerId attribute value in the app configuration. BloxOne EP Android version 1.0.10 and above use joinToken instead of customerId for authorization, for fresh installations on new devices the joinToken should be updated in the app configuration settings. Note: The customerId attribute will be removed from app in future versions. You may need to maintain both customerId and joinToken in your app configuration until such time all devices are update to 1.0.10 or above. |
Image 18
7. Click Next.
8. On the Android-config screen, click Publish to complete the installation and distribution process.
9. BloxOne Endpoint will be automatically installed on the client devices. The installation process might take several minutes to complete.
10. Open the BloxOne EP app on your device; on Android devices, find the app in the Work Profile. If prompted, accept the VPN acknowledgement. After a moment, the app will assume a protected state:
Image 19
