I was able to get a good connection with the Linux client but it is susceptible to the same password character and spaces bug. Also while it does work for me in Ubuntu I could not get it to work in the other distro I tested in and I think it has to do with certificates and where they are stored/how they are imported/etc
4.1.1 is out today and addresses several issues that were reported including the username/password lengths and special characters. We have tested and are able to get successful connections using spaces and long passwords.
We encountered the following issues with 4.1.0 that have been addressed in 4.1.1
Fixed an issue on MacOS endpoints where the GlobalProtect app couldn't detect processes that had more than 16 characters in their names.
Fixed an issue where end users who had special characters associated with XML markup (<, >, &, ', ") in their password couldn't connect to the GlobalProtect gateway after an upgrade to GlobalProtect app 4.1.0.
Fixed an issue where the GlobalProtect login prompt allowed only 24 characters for usernames and 21 characters for passwords. With this fix, you can enter up to 256 characters for usernames and passwords.
Fixed an issue on Windows endpoints where users couldn’t upgrade the GlobalProtect app using the Windows Installer (Msiexec) because the GlobalProtect setup file couldn’t overwrite existing GlobalProtect app software packages when the GlobalProtect service (PanGPS) was running.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!
The Live Community thanks you for your participation!