Configuring client-provided certificate enrollment settings
Applicable derived credential providers and device platforms
A client-provided certificate enrollment setting is necessary for each of the purposes an app uses derived credentials. These purposes are authentication, signing, encryption, and, for iOS only, decryption. For each app using derived credentials, the app’s AppConnect app configuration (or Web@Work setting or Docs@Work setting) refers to this certificate enrollment setting.
Procedure
|
1.
|
On the Admin Portal, go to Policies & Configs > Configurations. |
|
2.
|
Select Add New > Certificate Enrollment > Client-Provided. |
|
3.
|
Enter a name for the setting, such as Derived Credential Authentication. |
|
4.
|
Enter a description for the setting. |
|
5.
|
Select the purpose for the setting from the drop-down choices: Authentication, Decryption, Encryption, or Signing. |
Decryption is only supported for iOS devices.
|
6.
|
Select the appropriate derived credential provider from the drop-down choices. |
|
-
|
This field is applicable only for iOS devices. It has no impact on Android devices. |
|
-
|
If the selected derived credential provider is not available in Mobile@Work for iOS, the app becomes unauthorized. |
|
-
|
Each app can use only one derived credential provider for each purpose. |
Repeat these steps for each of the derived credential purposes your device users require.
Related topics