What is the Order of XenMobile Timeouts

book

Article ID: CTX224958

calendar_today

Updated On:

Description

Question:

What is the order of XenMobile Timeouts?

Answer:

Forced Time Out under  NetScaler gateway Session policies > Background Service Ticket > Session Timeout (NetScaler gateway OS session policies) > Max Offline Period(MDX app) > Inactivity Timer(client properties on XMS).
 

SettingComponentDefault SettingUltra Secure Settings (balanced to optimize user experience)Very Secure Settings Secure SettingsImplications
Session Time-outNetScaler Gateway1440 minutes720 minutes4320 (3 days)10080 minutes (7 days)When settings are tuned for optimal user experience:
Pros:
  • Users have a better experience because they aren't forced to continuously authenticate and check in to XenMobile.
  • Using the Inactivity Timer decreases security risks.
Cons:
  • Recommended timeout values allow devices to maintain open sessions without frequent re-authentication.
 
When settings are tuned for maximum security:
Pros:
  • Security is increased because users are required to authenticate to NetScaler Gateway and check in to XenMobile for compliance more often.
  • The settings ensure continued, regular monitoring of device compliance with policies defined in XenMobile.
 
Cons:
  • Users will be prompted frequently to authenticate.
  • Frequent authentication can be disruptive, depending on device policies (password and PIN requirements).
  • If using WorxMail (with NetWork Access of Tunneled to the internal network), email notifications may be delayed depending on re-authentication requirements.
 
Forced Time-outNetScaler GatewayOff1440 minutesOffOffOff
AuthenticationXenMobile Server (MDX Policy)Offline challenge onlyOffline challenge onlyOffline challenge onlyOffline challenge only
Maximum offline periodXenMobile Server (MDX Policy)72 hours (3 days)11 hours (1 hour less than NetScaler Gateway Session Timeout)71 hours (1 hour less than NetScaler Gateway Session Timeout)167 hours (1 hour less than NetScaler Gateway Session Timeout)
Background services ticket expirationXenMobile Server (MDX Policy)168 hours (7 days)168 hours (7 days)168 hours (7 days)168 hours (7 days)

Issue/Introduction

*

Powered by Wolken Software