...
The app config contains the following parameters:
- customerId
joinToken: The value in the XML file.
- groupName: In the Cloud Services Portal, the name of the group to which the endpoint will be moved. If the name is not present in the Cloud Services Portal, it will be added to the All BloxOne Endpoints group.
- userId: The unique name that identifies a mobile device. The configured name is displayed in the Cloud Services Portal, on the Manage > Endpoints page.
...
For Android, do the following:
Select the app and click the + button. The app config details will be displayed. Using the app config downloaded from the Cloud Services Portal, select each value and then click Save
:.
Image 6
The app config will look similar to the following: .
| Note | ||
|---|---|---|
| ||
|
Image 7
The assignment will be pushed to the device. If it is not installed, force-push it from System Manager > Apps > BloxOne EP.
2. Scroll down until the status is displayed.
3. Select the device, and click Push:
...
4. Open the EP app shown for the work profile on the Android device, and accept the VPN acknowledgement. After a few seconds, the app will be in a protected state:
Image 9
For iOS, do the following:
...
The app config will look similar to the following: .
| Note | ||
|---|---|---|
| ||
BloxOne Endpoint 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 11
The assignment will be pushed to the device. If it is not installed, force-push it from System Manager > Apps > BloxOne EP.
...
4. Open the BloxOne EP app on the iOS device, and accept the VPN acknowledgement. After a few seconds, the app will be in a protected state:
Image 13
