Reset Search



KB40225 - Pulse Secure Desktop client not automatically launch after SAML auth on Mac OS X

« Go Back


Last Modified Date1/17/2017 6:06 PM
This article describes an issue where Pulse Secure Desktop Client does not automatically launch after SAML authentication on Mac OS X 10.11.5 and up.
Problem or Goal
After authenticating with the Pulse Secure Desktop client on Mac OS X using SAML authentication, a Safari browser will launch to complete the VPN tunnel creation process.  Normally, once authentication is completed, the Safari browser window closes automatically and Pulse Secure Desktop client connection status is updated to "connected."  However, in this case, the user are redirected to the bookmark page in Safari browser and Pulse client does not completely connect until the user clicks Start button again from the bookmark page.  
This issue can occur when one of the following conditions are met:
  • Endpoint is running Mac OS X 10.11.5 update and above
  • Pulse Secure Desktop client version is running 5.1R9 and above
This issue is resolved in Pulse 5.1R10 and above.

Additionally, for Mac OS X 10.11.5 and up the Mac user will need to enable Allow JavaScript from Apple Events from the Develop menu in Safari.

Note:  This is due to changes made in this OS X update that disabled certain services that the Pulse client is dependent upon to complete the VPN connection.  For OS X versions prior to the 10.11.5 update these settings should already be enabled by default.

Follow these steps to display the Develop Menu in Safari to enable JavaScript.
  1. Launch Safari
  2. From the taskbar, click Safari > Preferences
User-added image
  1. From the top menu, click Advanced 
  2. Towards the bottom, click the checkbox for Show Develop menu in menu bar
User-added image
  1. Once completed, Develop menu will appear between the Bookmarks and Window menu items.
User-added image
  1. From the taskbar, click Develop menu
  2. Enable Allow JavaScript from Apple Events.
User-added image

Pulse Secure does plan to implement a new feature to perform SAML authentication from a embedded browser session within Pulse instead of using the default Safari browser.  Currently, there is no ETA on this feature.  The KB will will be updated once more information is available.
Related Links
Attachment 1 
Created ByTravis Bradbury



Was this article helpful?



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

Characters Remaining: 255