Pulse Desktop Client. Release Notes PDC 5.3R1.1 Build 755. Release, Build Published Document Version. 5.3R1.1, 755 May,

Transcription

1 Pulse Desktop Client Release Notes PDC 5.3R1.1 Build 755 Release, Build Published Document Version 5.3R1.1, 755 May,

2 Contents Introduction... 3 Interoperability and Supported Platforms... 3 General Notes... 3 Caveats, Important Changes, and Deprecated Features... 3 Upgrade Paths... 3 Fixed Issues in Current 5.3R1.1 Release... 4 New Features in 5.3R1 Release... 4 Fixed Issues in 5.3R1 Release... 5 Known Issues in 5.3R1 Release... 5 Documentation... 8 Documentation Feedback... 8 Technical Support... 8 Revision History by Pulse Secure, LLC. All rights reserved 2

3 Introduction This release-notes document for the Pulse Secure desktop client version 5.3R1.1. This document provides a cumulative list of all enhancements, fixes and known issues for the 5.3R1.1 client. If the information in the release notes differs from the information found in the documentation set, follow the release notes. The Pulse Secure desktop client provides a secure and authenticated connection from an endpoint device (either Windows or macos) to a Pulse Secure gateway (either Pulse Connect Secure or Pulse Policy Secure). For a complete description of the capabilities of this desktop client, please see the online help within the desktop client itself, or the Pulse Desktop Client Administration Guide (which can be found at Pulse Secure s Technical Publications site). Interoperability and Supported Platforms Please refer to the Pulse Desktop Client Supported Platforms Guide for supported versions of operating systems, browsers, and servers in this release. General Notes Security-related issues are not normally covered in Pulse Secure release notes. To find more information security advisories affecting Pulse Secure products, please the Pulse Secure security advisory page. Caveats, Important Changes, and Deprecated Features Please note that client upgrades are not supported to or from Beta releases. As such, if you participated in the 5.3r1 Pulse Secure desktop client Beta program, please un-install the Beta 5.3r1 client before attempting to install any subsequent Pulse desktop client releases. Important note: In order to run the Pulse Secure desktop client version 5.3r1 or later on a Windows 7 machine, the machine must contain a March 10, 2015 Windows 7 Update in order to be able to accept and verify SHA-2-signed binaries properly. This Windows 7 update is described here and here. If this update is not installed (in other words if a Windows 7 machine has not received an OS update since March 10, 2015), then Pulse 5.3R1 and later will have reduced functionality (see , below). (As a general rule, Pulse Secure, LLC recommends that client machines be kept current with the latest OS updates to maximize security and stability.) Upgrade Paths The following table describes the tested upgrade paths. Release 5.2Rx You can upgrade directly to 5.3R Rx or 5.1Rx You can upgrade directly to 5.2Rx simply by installing the 5.2Rx update by Pulse Secure, LLC. All rights reserved 3

4 Fixed Issues in Current 5.3R1.1 Release The following table lists issues that have been fixed and are resolved by upgrading to this release. Release Note Unable to load captive portal properly when captive portal page uses any technology above IE Lock/unlock mode switching doesn't happen in some scenarios Captive portal redirection is not working with Canada Starbucks New Features in 5.3R1 Release The following table describes the major features that are introduced in this release. Feature Minimum client Version Enforcement IPv6 support for 802.1x authentication - Windows and MAC VPN only Access (Windows) IPv6 Spilt Tunneling for Windows It allows to easily force end users to upgrade their clients to some specified minimum version. If a client that is older than a certain version is used to connect to the Pulse Connect Secure gateway, the end user is prompted to upgrade their client, rejecting which the connectivity is denied. This feature is to enable Pulse Desktop client to authenticate Pulse Policy Secure with 802.1x L2 connection over both IPV4 and IPV6 on both Wired and Wireless networks. VPN only access is an extension to our existing Always ON VPN and adds flexibility to the function, by letting users be in control of when they want to access the VPN. When a user is not connected to the VPN, all network access is blocked. When a user needs to access something on the network, they must sign into the VPN, and in successfully doing so, get the network access allowed by IT. Pulse VPN now allows accessing both IPv4 and IPv6 corporate resources from IPv4 and IPv6 endpoints. It enable client to access both corporate network and local network at the same time. The network traffic designated are directed to tunnel interface for corporate network by configuring route policies, whereas other traffics are sent to direct interface Pulse Linux Support for Debian Systems In spirit of providing broad platform support for our customers, we have now added Debian Linux as a validated platform, to an existing list if supported Linux platforms. Windows 10 Redstone support Complete support for Windows 10 Redstone by Pulse Secure, LLC. All rights reserved 4

5 Feature Certificate authentication in Pulse Linux It allows secure and seamless user experience when setting up VPN tunnel. Fixed Issues in 5.3R1 Release The following table lists issues that have been fixed and are resolved by upgrading to this release. Release Note Always on VPN doesn't work on 32 bit machines Pulse Linux: OpenSSL Security Advisory Location awareness rules are not taken into consideration when "VPN only access" is turned on VPNOnlyAccess doesn't kick in the firewall after reboot when the connection is not marked as automatic OpenSSL Security Advisory Error while installing Pulse desktop client in Linux Debian Rebranding required for "ConfigureInstaller" file of Pulse Secure Desktop Client-5.2R Branding Tools contains incorrect data in PulseResource_JA.txt for label Known Issues in 5.3R1 Release The following table lists Known issues in 5.3R1 release Pulse client 5.3R1 End user help doesn t have the Localization for Pulse5.3R1 Features. Certificate Authentication is failing on MacOS when "Always Trust" option is enabled on the client machine by Pulse Secure, LLC. All rights reserved 5

6 Select Use System Defaults instead of Always Trust option on endpoint which is the default option. Navigate to Keychain Access->Login->select the certificate->right click->get info and choose Use System Defaults on endpoint Active Users page does not capture the Mac OS version for Pulse connections Sometimes Disconnect is taking more time on MacOS Restart Pulse service. Pulse client is not going for auto connect after signing out from the browser when AlwyasOn- VPN is enabled User can connect back using browser. Pre-sign-in notification message not being displayed when number of characters exceed 2883 characters. With OPSWAT V4 SDK when remediation action is going for turn on RTP, in Pulse UI displaying Update in Progress. Inconsistency may observe when using certificate authentication on cent OS 6.4. The setup client alert message which display during the minimum client enforcement is not localized.. Pulse client Localization is not working for Windows8, windows8.1 and Windows10 Minimum client enforcement feature is not supported for Pulse5.1Rx and older clients. Inaccurate statistics sent to accounting server when layer 3 VPN is formed with Pulse client Condition: Accounting bytes updated in LMDB cache is not correct, there by showing wrong accounting bytes Upgrading Pulse from 5.2R5 (or prior) to 5.2R6 on Linux shows "downgrading" Pulse Desktop Client installation via browser failing for few Win7 Professional machines Direct MSI installer instead of browser for pulse desktop client 2017 by Pulse Secure, LLC. All rights reserved 6

7 Connection set xml import failing from 8.1Rx to.8.3r1 Condition: Import from 8.1R10 or 8.1R11 to 8.3R1 Import from 8.2R5 to 8.3R1, import fails if 8.3R1 has a new connection with the same connection name as in 8.2R5 Import binary or add below option tag with mentioned content in xml file under each connection and import it to 8.3R1. <option> <name>lock down this connection</name> <description>network access is limited until this connection is established. This option is available only when the Always-on Pulse Client option or VPN only access option on the connection set is checked.</description> <tag>connection-lock-down</tag> <bool-type> <value>false</value> </bool-type> </option> Import from 8.2R5 to 8.3R1, import fails if 8.3R1 has a new connection with the same connection name as in 8.2R5. Modify description for Lock down this connection to "Network access is limited until this connection is established. This option is available only when the Alwayson Pulse Client option or VPN only access option on the connection set is checked." 2017 by Pulse Secure, LLC. All rights reserved 7

8 Documentation Pulse documentation is available at Documentation Feedback We encourage you to provide feedback, comments, and suggestions so that we can improve the documentation. You can send your comments to Technical Support When you need additional information or assistance, you can contact Pulse Secure Global Support Center (PSGSC): Call us at (toll-free USA) For more technical support resources, browse the support (website Revision History The following table lists the revision history for this document. Table 6 Revision History Revision Date 2.0 May, R1.1 Update 1.0 March, 2017 Initial Publication 5.3R by Pulse Secure, LLC. All rights reserved 8