Prefilled sign-in for staff
People only confirm their sign-in. The email comes from your MDM and the domain is added when needed.
{
"login_hint": "jsmith@example.com",
"login_domain": "example.com"
}Android app directory · Communication
These are the managed app configuration keys Cisco documents for the Webex app on Android. They help IT prefill sign-in details, block external users from the unmanaged app, turn on a PIN lock and limit what the app reads from the device. Some keys are for Cisco Unified Communications Manager calling or FedRAMP environments and only matter in those cases. Cisco's Intune build, Webex for Intune, has its own package name (com.cisco.wx2.android.msintune) and is not covered here.
com.cisco.wx2.android Common setups
Copy a setup into the managed configuration of a policy, then adjust the values. Each one uses only keys explained below.
People only confirm their sign-in. The email comes from your MDM and the domain is added when needed.
{
"login_hint": "jsmith@example.com",
"login_domain": "example.com"
}Set your Control Hub organization ID, which Cisco ties to blocking external users from the unmanaged app, and add a PIN lock.
{
"orgIdentifier": "your-org-id",
"pinLockEnabled": true
}Block the app from accessing the calendar and contacts on the device, useful on shared or regulated devices.
{
"isLocalCalendarDisabled": true,
"isLocalContactsDisabled": true
}Managed configuration
Key names and value types come from the vendor’s documentation. The explanations are written by Nomid.
| Key | Type | What it does | Example |
|---|---|---|---|
| Sign-in and organization | |||
login_hint | Email address or variable | Pre-fills the sign-in email so people do not type it. Map your MDM's user email variable to this key. | jsmith@example.com |
login_domain | Domain name | Automatically appends the domain to the user name someone enters, which is handy when staff sign in with short names. Cisco lists it for Android. | example.com |
orgIdentifier | Control Hub organization ID | Sets your Control Hub organization ID. Cisco ties it to a restriction that blocks external users from the unmanaged Android app, so your people use a managed copy. | your-org-id |
fedRampEnabled | On or off | Sends people to the sign-in cluster for Webex for Government customers. Only relevant for FedRAMP organizations. | false |
| Security and device access | |||
pinLockEnabled | On or off | Turns on a PIN lock for the app on Android. Cisco documents it as a boolean. | true |
isLocalCalendarDisabled | On or off | Blocks the app from accessing the device calendar, which suits shared or regulated devices. | true |
isLocalContactsDisabled | On or off | Blocks the app from accessing device contacts. | true |
| Cisco Unified Communications Manager calling | |||
VoiceServicesDomain | Domain name | The voice services domain for Cisco Unified Communications Manager calling. | voice.example.com |
AutoLoginUserName | User name | Enters the Cisco Unified Communications Manager account user name so people do not type it. | jsmith |
AutoLoginUserPassword | Password | Enters the Cisco Unified Communications Manager account password. Avoid storing a shared password in your MDM when you can. | |
Deploy with Nomid
Find it on Google Play from the policy’s apps list and choose how it is installed.
In the policy, set the app’s managed configuration with the keys and values from this page.
Devices in the policy receive Webex and its configuration on their next sync.
Questions
com.cisco.wx2.android. Cisco's Intune article names a separate Intune build, Webex for Intune, with the package name com.cisco.wx2.android.msintune.
It sets your Control Hub organization ID. Cisco says it is used with the restriction that blocks external users from using the unmanaged Android app, so your people must use a managed instance.
The VoiceServicesDomain, AutoLoginUserName and AutoLoginUserPassword keys are described by Cisco as settings for Cisco Unified Communications Manager. If you do not use that service, you can leave them out.
In its Intune article, Cisco says the app checks for the settings when people run it for the first time on their devices. Cisco does not repeat this for other MDMs, so test with your own.
Add the app to a Nomid policy, set its configuration and choose its permissions.