Handling app-specific configuration from the Ivanti server
Handling app-specific configuration from the Ivanti server requires some application development before wrapping the app. If you do not use this feature, develop your app to set up its configuration as you typically would. For example, set up the app to prompt the device user for configuration settings.
You determine the app-specific configuration that your app requires from the Ivanti server. Examples are:
- the address of a server that the app interacts with
- whether particular features of the app are enabled for the user
- user-related information from LDAP, such as the user’s ID and password
- certificates for authenticating the user to the server that the app interacts with
Each configurable item is a key-value pair. Each key and value is a string. A server administrator specifies the key-value pairs on the server for each app. The administrator applies the appropriate set of key-value pairs to a set of devices. Sometimes more than one set of key-value pairs exists on the server for an app if different users require different configurations. For example, the administrator can assign a different server address to users in Europe than to users in the United States.
When the value is a certificate, the value contains the base64-encoded contents of the certificate, which is a SCEP or PKCS-12 certificate. If the certificate is password encoded, the server automatically sends another key-value pair. The key’s name is the string <name of key for certificate>_MI_CERT_PW. The value is the certificate’s password.
For more information on implementing this feature in your app, see Handling AppConnect app-specific configuration.