KB29135 - Unable to pass traffic through Pulse Secure Mobile Client on iOS after upgrade to Pulse 5.0.4.46105

This article describes an issue and provides a solution for iOS users that are unable to pass traffic with Pulse Mobile version 5.0.4.46105.

Unable to pass traffic through Pulse Secure Mobile client for IOS after upgrade to 5.0.4.46105 when the following criteria is met:

• The PPS or PCS appliance is configured with AES or 3DES with 128 bit or 168 bit Cipher Suite (System > Configuration > Security > SSL options).

• The Pulse Secure Mobile client on iOS is configured to connect using SSL Transport mode (Users > Resource Policies > VPN Tunneling > Connection Profiles)

NOTE: If DES is configured, then Pulse Secure mobile client may not be able to connect at all.
NOTE: This issue may still occur if the Connection Profile is configured to use ESP and the Pulse Secure mobile client is unable to connect using ESP and the transport fallsback to using SSL.

This issue resulted from changes made when Per App VPN support was added to Pulse Secure mobile client for iOS 5.0R4.

The issue is fixed in Pulse Secure mobile client for iOS 5.0r5 and up.   

Workaround:

Enable only RC4 Encryption:

1. In the Admin UI Select System > Configuration > Security > SSL options
2. Choose Custom SSL Cipher Selection
3. Select only RC4 Cipher.
4. Uncheck all other Cipher options besides RC4.
5. Select Save Changes.

NOTE: This change will cause all currently connected Network Connect and Pulse Secure Desktop Client tunnels to disconnect and reconnect momentarily in order to use the new encryption option.  Therefore, consideration should be taken to perform this operation during a short maintenance window.


 

Pulse Secure Desktop Client for Mobile Devices - Documentation