Reset Search
 

 

Article

KB44592 - Pulse Desktop macOS Client Open Issues on BigSur

« Go Back

Information

 
Last Modified Date9/22/2020 5:59 AM
Synopsis

Pulse Desktop macOS Client Open Issues on BigSur

This article outlines the list of all Open & Known issues on BigSur (macOS 11) and a workaround.
Problem or Goal
We have been testing Pulse Desktop macOS Client 9.1R8.2 on BigSur (macOS 11) Beta releases and few issues and their workarounds have been identified. 
 
Cause
Solution

The following are the list of Open & Known issues observed so far and and their workarounds:

Known Issue 1: Pulse Desktop mac Client 9.1R8.2 cannot be distributed via PCS that runs version prior to 9.1R8.2 without Manual installation of PSSetupClientInstaller.dmg

 

Impact

Admin cannot distribute Pulse Desktop mac Clients from PCS server running version prior to PCS 9.1R8.2.

End User Symptoms

End Users will see the following error during upgrade/installation if Admin deploys Pulse 9.1R8.2 package on the PCS running Pre-9.1R8.2
User-added image

Root Cause

System Extension requires
Notarization and this gave rise
to certificate dependencies.

Workaround

Manually install PSSetupClientInstaller.dmg if PDC (mac) 9.1R8.2 needs to be distributed via PCS versions prior to 9.1R8.2 (Check in the attachment section).

Plan to Fix

Under Consideration

Pulse Bug

PRS-394581



Known Issue 2: When Lockdown Mode is configured, traffic other than TCP/UDP ProtocolUnicast Local Address and Unicast Remote Address will not be blocked (e.g. ICMP)

Impact

Network Traffic types other than TCP/UDP ProtocolUnicast Local Address and Unicast Remote Address will not be blocked in Lockdown Mode, as those rules cannot be applied.

End User Symptoms

End Users will be able to access Network resources other than TCP/UDP ProtocolUnicast Local Address and Unicast Remote Address in Lockdown mode.

Root Cause

mac OS API Limitation

Workaround

N/A

Plan to Fix

Waiting on Apple

Pulse Bug

PRS-394150



Known Issue 3: When Lockdown Mode is configured Apple, Embedded browser pops up when pulse user is in a captive portal environment.

Impact

When lockdown mode is configured Apple, Embedded browser pops up when pulse user is in a captive portal environment

End User Symptoms

 

Unwanted Apple embedded browser popup is shown:

User-added image

The user has to close this prompt, and then the Pulse embedded browser prompt appears as shown below:

User-added image

 

Root Cause

 

Due to macOS security restrictions, Apple Captive portal is presented to the end user.

 

Workaround

Manually close the Apple embedded browser

Plan to Fix

Waiting on Apple

Pulse Bug

PRS-393958


Known Issue 4: When Lockdown Mode is configured Apple, Embedded browser pops up when pulse user is in a captive portal environment.

Impact

User experience will be affected

End User Symptoms

End User will see a dialog box similar to the one below:

User-added image

Root Cause

Due to macOS security restrictions, Apple Captive portal is presented to the end user.

Workaround

Close the Pulse embedded browser instead of proceeding.

Plan to Fix

Waiting on Apple

Pulse Bug

PRS-393971


Known Issue 5: When Lockdown Mode is configured Apple, Embedded browser pops up when pulse user is in a captive portal environment.

Impact

Captive portal functionality will have an impact 

End User Symptoms

End User will see a dialog box similar to the one below:
User-added image

Root Cause

Due to macOS security restrictions, Apple Captive portal is presented to the end user.

Workaround

Close the Pulse embedded browser instead of proceeding.

Plan to Fix

Waiting on Apple

Pulse Bug

PRS-393969


Known Issue 6: Pulse shows kernel extension blocked message post upgrade to BigSur for Pre-9.1-R8.2 PDC versions.

Impact

Operation of Traffic Enforcement and Lockdown Mode is affected

End User Symptoms

If PDC <9.1R8.2 is installed and the user upgrades macOS to BigSur, the following message is shown:
User-added image

The PDC's Kernel Extension is prevented from loading and Lockdown/Traffic Enforcement will not work properly.

Root Cause

PDC versions prior to 9.1R8.2 contain Kernel Extensions, which are no longer supported in Big Sur.

Workaround

Install PDC 9.1R8.2

Plan to Fix

N/A

Pulse Bug

PRS-394016 


Known Issue 7: [Catalina & above] New System Extension install flow requires explicit end-user approvals

Impact

User prompts need to be accepted to activate PDC system extension (Firewall) component

End User Symptoms

The user will see a first prompt to allow "Pulse Secure" application load, and a second prompt to approve "Network Filtering". In both cases credentials are required.  
User-added image
User-added image

Root Cause

User approval of System Extensions (part of PDC starting in Catalina) is required as per macOS design

Workaround

N/A

Plan to Fix

This is a macOS limitation.

Pulse Bug

PRS-393513


Known Issue 8:  [Catalina & above] Pulse system extension remains on systemextensionsctl list even after uninstall and immediate reboot
 

Impact

No User Impact (Pulse reinstall will not have impact)

End User Symptoms

To verify use the command "systemextensionsctl list" that shows the state as "uninstalling"
User-added image

Root Cause

macOS Limitation

Workaround

N/A

Plan to Fix

N/A

Pulse Bug

PRS-393498


Known Issue 9:  On-Demand Pulse system extension with Traffic Enforcement is not supported (Pulse System Extension will be present as long as Pulse is installed)

Impact

No functional impact to the user

End User Symptoms

Pulse System extension process keeps running post reboot when when Traffic Enforcement or Lock Down mode was previously activated for the user.

Root Cause

macOS design/Limitation

Workaround

N/A

Plan to Fix

N/A

Pulse Bug

PRS-394339


Known Issue 10:  Catalina & above] Uneven VPN Performance.

Impact

May impact VPN Performance sometimes

End User Symptoms

Inconsistent throughput during download and upload may be observed.
 

Root Cause

macOS issue

Workaround

N/A

Plan to Fix

Waiting on Apple

Pulse Bug

PRS-392565


Known Issue 11:  Pre-9.1R8.2 Pulse Clients on BigSur won't notify end users (who have LockDown configured) that KeXT (Kernel Extension) isn't supported.

Impact

May impact VPN Performance sometimes

End User Symptoms

Users will be able to connect successfully without the Firewall Rules being applied.

Root Cause

macOS limitation

Workaround

Move to Pulse 9.1R8.2

Plan to Fix

Waiting on Apple

Pulse Bug

PRS-394012

 

Known Issue 12:  Gibberish message is shown on chrome before re-directing to PSAL download page

Impact

Sometimes on Chrome browser before re-directing to PSAL download page, a gibberish value is shown in a popup.

End User Symptoms

User will see a message similar to the one shown below:
User-added image

Root Cause

Work in Progress

Workaround

Refresh the page or use Safari instead of Chrome

Plan to Fix

Under Consideration

Pulse Bug

PRS-394703

 

Known Issue 13:  PDC System Extension cannot be Authorized/approved after several Installations/Un-installations on Bigsur.

Note: This issue has been reported by other Application Vendor as well.

Impact

Users cannot Authorize/approve PDC System Extension.

End User Symptoms

Users will get the following error when opening : System Preference > Security & Privacy.
User-added image

Root Cause

MacOS process that handles
System Preferences crashes i.e.
com.apple.preference.security.remoteservice. Same issue has been reported by other vendors as wellhttps://developer.apple.com/forums/thread/660670

Workaround

This error is shown until Pulse Secure application is uninstalled.

Plan to Fix

Waiting on Apple

Pulse Bug

PRS-394896


We will update this section as and when we have more results and the final update will come in when BigSur is officially released.



 
Related Links
Created ByRaghu Kumar

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255