This deb has the correct checksum. So this is official PulseSecure client for Ubuntu. I manually downloaded the certificate and installed in my cert store. To get rid of the message about the unwanted TLS certificate. IMHO the client should be able to do this for the user rather than the other way around. After that I can see the portal page which asks for username and token same as on MS Windows. When I provide those, the portal window closed without message or error. Using route -n I can look at the routing table and see that the client is not working. So it seems to be crashing without error messages. From file menu I can go to the "advanced" status overview which only shows the message "This session is not connected". So this confirms my suspicion that this client is not working. Any suggestions on how to troubleshoot the workings of this client? There is not logging, error message or anything to get an idea on all things that are wrong with this approach. BTW when I go to the portal using FireFox on Ubuntu I can logon. When I try to start one of the remote connections it doesn't detect the installed client but rather offers an alternative download. A deb-zip file PulseSecureAppLauncher.deb.zip. This contains a deb file PulseSecureAppLauncher.deb and a script Installer.sh. So as it turns out I think the admin has actually started to become creative trying to compensate for the lack of support for Linux / Ubuntu when using PulseSecure as a security solution and the obvious problems and bugs in the official client.
... View more
