When connecting to my Company VPN Profile on Linux Mint I get a Chromium Embedded Browser install failure: "CEF package sha1 verfication failed"
Please can someone assist?
I have a case open about this. Pulse is pulling down CEF from Spotify and Spotify moved CEF files arounds, renamed them and the SHA1 changed. Also, the DNS record "opensource.spotify.com" appeared to be removed or down for about a week and after it started resolving again, I noticed the CEF downloads were moved.
Thank you Sir. Please let me know if they come back to you with a fix? Its quite disturbing how Pulse treat their Linux users.
We have the same issue in our organization. Last week there was a different error message when trying to instal the embedded client. I have a ticket open with PulseSecure that's been dragging for awhile.
As a temporary workaround until Pulse release a new version; you can modify /opt/pulsesecure/bin/setup_cef.sh and change this line
then run ./setup_cef.sh install
in case the URL is cut
Thank you the CEF was installed but the screen which comes up when establishing connection remains blank and then times out. Its as if there is meant to be buttons displayed to complete the connection which isnt showing up
Anyone have this issue and a possible work around?
Hi @zanyterp, I got the same error from Pulse Secure 18.104.22.16883 installed on Ubuntu 20.04 LTS. This Ubuntu release is a non-mint release. I also tried to install by root besides by plain user, but I still got the error.
Can you tell me how to fix it? Thanks!
which release are you using? are you looking at 9.1R11?
can you test with a non-mint release (ubuntu or centOS) to see if it is working on the versions officially supported?
9.1r11 fixed the install issue and things worked fine for about a month. All of a sudden things broke for everyone (30 users?). The embedded browser seems to do its thing but it stalls after the last MFA approval. Both Azure and PulseSecure system logs show authentication success but the embedded browser stalls and the causes a fault in the PulseUI. I worked with PulseSecure support and they say it's definitely a bug that will be fixed in 9.1r12, which is due out late April.