This section provides information of the custom and the default SDK configurations.
Default vs Custom SDK Profiles
When you configure your application, you select a custom or a default application profile. This action applies an SDK profile to the application, giving deployed Workspace ONE UEM applications additional features.
To ensure that your application configuration runs smoothly, it is helpful to:
- Know the difference between a Custom and Default SDK profile.
- Determine if a Custom or a Default SDK profile is more appropriate for your application.
- Ensure you have configured the SDK profile type that you want to apply.
Use the following chart to determine if you want to apply a Default or Custom SDK profile to your application, and to direct you to the configuration instructions for the profile you use.
You can define SDK profiles using two different profile types: Default or a Custom SDK application profile.
|Implementation||Share SDK profile settings across all applications set up at a particular organization group (OG) or below.||Apply SDK profile settings to a specific application, and override the Default Settings SDK profiles.|
|Advantage||Provides a single point of configuration for all your apps in a particular OG and its child groups.||Offers granular control for specific applications and overrides the Default Settings SDK profiles.|
|Read More||Continue reading this section to learn which default SDK profiles apply to deployed apps.||Learn more about custom SDK profile settings in the VMware Workspace ONE UEM Mobile Application Management Guide on docs.vmware.com.|
Custom SDK Profile Settings
Custom SDK settings are available to address cases where a single app needs to exhibit unique behaviors that differ from the rest of the app suite.
Workspace ONE UEM recommends using default settings for ease of maintenance and a consistent end user experience between Workspace ONE UEM and wrapped apps. However, Custom SDK setting are available to address cases where a single app needs to exhibit unique behaviors that differ from the rest of the app suite.
Enable Custom Applications Settings to override default SDK settings, and configure unique behaviors that only apply to a single app.
|Authentication Method||Defaults to Single Sign-On. Ensure you require MDM enrollment so that Single Sign-On can function properly.|
|iOS Profile||Select a custom-created SDK profile from the drop-down list the settings profile for iOS devices.|
|Android Profile||Select a custom-created SDK profile from the drop-down list the settings profile for Android devices.|
|Use Legacy Settings and Policies||Only enable legacy settings if directed to do so by a Workspace ONE UEM representative. Legacy settings do not leverage Shared SDK profile settings and should only be implemented in certain edge cases.|
|Default Authentication Method||Select the authentication method for the applications.|
|Enable "Keep me signed in"||Enable to allow end users to remain signed in between uses.|
|Maximum Number of Failed Attempt||Set the number of passcode entry attempts allowed before all data in the VMware Workspace ONE Content is wiped from a device and the device is enterprise wiped.|
|Authentication Grace Period (min)||Enter the time (in minutes) after closing the Workspace ONE Content before reopening the Workspace ONE Content will require users to enter credentials again.|
|Prevent Compromised Devices||Enable to prevent compromised devices from accessing Workspace ONE Content.|
|Enable Offline Login Compliance||Enable to allow offline login compliance.|
|Maximum Number of Offline Logins||Enter the number of offline logins allowed before you have to go online.|
Expected Behavior for SDK Authentication
|Authentication Type||SSO||Sessions||Credentials||Expected Behavior|
|Disabled||Enabled||Single||Enrollment Credentials||Open apps without prompting end users to enter credentials.|
|Passcode||Enabled||Single||Passcode||Prompts at first launch of first app, establishing a single app session. The next authentication prompt occurs after the session times out.|
|Username and Password||Enabled||Single||Enrollment Credentials||Prompts at first launch of first app, establishing a single app session. The next authentication prompt occurs after the session times out.|
|Passcode||Disabled||Per App||Passcode||Prompts on a per app basis, establishing individual app sessions. Note that each app may have a unique passcode. The next authentication prompt occurs when launching a new app, or an individual app session times out.|
|Username and Password||Disabled||Per App||Enrollment Credentials||Prompts on a per app basis, establishing individual app sessions. The next authentication prompt occurs when launching a new app, or an individual app session times out.|