Avalanche powered by Wavelink

This page refers to an older version of the product.
View the current version of the User Guide.

App Wrapping Settings Payload (Android/iOS)

As part of the App Wrapping process, an App Wrapping Settings payload is designed to enhance the security of private apps and configures settings for how a Smart device handles applications that are wrapped by Avalanche. Prior to setting up this payload, you must have apps wrapped through the Software Payload (Android/iOS/Windows Phone). Once your apps are wrapped, you can use this payload you can prevent wrapped apps from launching on compromised devices, restrict the transfer of copied text between a wrapped and non-wrapped app, and set authentication intervals that require the user to log in with their authorized email address and password after periods of inactivity. Wavelink recommends utilizing this payload if you have wrapped apps, as this will increase the security of corporate data handled in the app itself.

You can configure only one App Wrapping Settings payload for a device. This payload has the following options:

Payload Name	The name of the payload.
Restrict Copy/Paste	When copy/paste is restricted, the user cannot copy from a secured app to an unsecured app. However, the user can copy from unsecured apps to a wrapped app or between two wrapped apps.
Require Secure Communication	Forces the traffic for the application to go through the CSA/SOCKS server that is installed with LANDESK Mobility Manager. The service must be activated to use this option. To use this setting, you need LANDESK Management Suite 9.6+. For more information, see Enabling LANDESK CSA/SOCKS Service.
Disallow app on compromised device	Prevents the app from being launched on a device that has been rooted or jailbroken.
Idle Authentication Timeout	Indicates the maximum amount of time a user can leave the app idle during an authenticated session. If a user launches a wrapped app and then multitasks to another app or locks the device for more than this amount of time, they are prompted to authenticate the next time they access the wrapped app. This setting is similar to the Wrapped Apps force authentication setting on the System Settings page. However, the idle authentication timeout applies only when a user launches a wrapped app. The company-wide setting on the System Settings page is active whether or not the user has recently authenticated or launched a wrapped app. When determining an idle timeout period, you must set it to less than the forced authentication interval set from the System Settings page. That way the user will not be forced to authenticate before the idle timeout elapses. For information on the force authentication setting, see Configuring General System Settings.