The user will need to configure the permissions on AirWatch. Choose any of the following options:
The created account may need to call the REST API to collect information, and some configuration in the AirWatch console is needed.
This option needs configuration from the TMMS web console and the AirWatch console.
For settings that will be changed in the AirWatch console, refer to this article: Configuring the auto-launch function of the Mobile Security (TMMS) for Enterprise Android agent using AirWatch.
This option allows the administrator to select specific REST APIs to be used.
The table below shows the specific REST APIs that TMMS use, and should be enabled:
| Category | Name |
|---|---|
| Admin User Management | Search Admin User |
| WTag Management | Create Tag |
| Search Tag | |
| Add Devices to the Tag | |
| Remove Devices from Tag | |
| Retrieve Devices with Specific Tag | |
| Smart Group Management | Create Smart Group |
| Search Smart Groups | |
| Delete Smart Groups | |
| Application Group Management | Create Application Group |
| Search Application Group | |
| Retrieve Application Group Details | |
| Add Application to an Application Group | |
| Delete Application from the Application Group | |
| Application Management | Internal Application Install : Upload Application Chunks (iOS and Android) |
| Internal Application Install : Begin Internal Application Install | |
| Device Management | Retrieve Device Information |
| Device Extensive Search | |
| Device Count Info |
The AirWatch REST permission settings page does not have permission for each API, but provides a lot of API Series (e.g. Admin API, APPs API, etc.). End-users will need consult with AirWatch regarding what REST API permission need to be enabled in the settings page.