Configure the Mobile Apps with the Mobile Device Management
Mobile Device Management, hereafter abbreviated as MDM, can help you with the following tasks:
- Deploying mobile apps on devices
- Managing the deployed mobile apps
- Configuring the mobile app options
Prerequisites
- Configured MDM solution
- Mobile device that is enrolled in the MDM
Configuration
Use the following apps’ IDs to start managing the mobile apps.
- Android: com.ysoft.ysoftsafeq
- iOS: id1617032214
Then you can use the following examples to import the configuration options into your MDM solution and replace individual options with your values or enter the wanted configuration options from the table below manually.
For Android:
Cloud environment config example
{
"domain_name": "REPLACE_DOMAIN"
}
Alternative environment config example
{
"client_id": "REPLACE_WITH_CLIENT_ID",
"issuer": "REPLACE_WITH_ISSUER",
"api_server": "REPLACE_WITH_API_SERVER"
}
For iOS:
Cloud environment config example
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>user_domain</key>
<string>REPLACE_WITH_USER_DOMAIN</string>
</dict>
</plist>
Alternative environment config example
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>issuer</key>
<string>REPLACE_WITH_IDENTITY_PROVIDER_URL</string>
<key>api_server</key>
<string>REPLACE_WITH_API_ENDPOINT</string>
<key>client_id</key>
<string>REPLACE_WITH_CLIENT_ID</string>
</dict>
</plist>
Available options to configure apps’ values from the login form:
Managed Cloud Environment Configuration Value | Required | Data Type | Default Value | Example | Explanation |
---|---|---|---|---|---|
domain_name | 🔴 yes | String | — | “your.domain” | Address of your cloud print management solution. |
client_secret | ⚪ optional | String | — | “XZmTxYCdMZJRNurFGzTeeZVsJqI” | API key that authenticates the app. |
fully_managed | ⚪ optional | Bool | true | true | Disables any user interaction with the login form when set to true. |
Managed Alternative Environment Configuration Value | Required | Data Type | Default Value | Example | Explanation |
---|---|---|---|---|---|
issuer | 🔴 yes | String | — | “https://your.domain/oauth/v1” | Identity provider URL |
api_server | 🔴 yes | String | — | “https://your.domain” | API endpoint |
client_id | 🔴 yes | String | — | “mobile-client” | Client ID |
client_secret | ⚪ optional | String | — | “XZmTxYCdMZJRNurFGzTeeZVsJqI” | API key that authenticates the app. |
allow_invalid_certificates | ⚪ optional | Bool | false | false | Disables validation of the server certificates when set to true. |
fully_managed | ⚪ optional | Bool | true | true | Disables any user interaction with the login form when set to true. |
Limitations
If you deploy a valid configuration for both – cloud and alternative environment – only cloud environment will be set.
If you don’t deploy all the required values, managed configuration won’t be used.
Deploying new configuration will log out already logged-in users and apply the newly deployed values on Android.