I have been able to confirm that the Sophos connect client 2.1, using RADIUS for authentication and the user has a space in their password, it will not authenticate the SSL VPN Connection.
The initial login to the web portal (with the CAPTHA option) to download the SSL VPN Policy will work just fine and can download the policy without issue. When it goes to connect the VPN, the login will fail. Removing the space in the password resolves the issue.
Thank you for contacting the Sophos Community.
There’s a similar issue investigated under NCL-1319 and fixed on Sophos Connect 2.2 where if the Auto-provisioning will fail if the password…
There’s a similar issue investigated under NCL-1319 and fixed on Sophos Connect 2.2 where if the Auto-provisioning will fail if the password has spaces, this is because Sophos Connect doesn't support spaces in the password field.
Do we have a projection on when version 2.2 will be out? I'm facing this issue as well. SSL-VPN provisioning profile also doesn't work properly on 18.0-mr5 either. Importing ovpn user profile does still work in SC 2.1.
2.2 is targeted to be released after the ZTNA Agent becomes GA, currently, ZTNA is in stage 2 of EAP.
This really needs to be fixed ASAP. I wasted a lot of time trying to get the VPN working on my new laptop until we found this article. It's caused issues with other users as well. This is unacceptable. I tell users to use passphrases and then this comes along....
yes, this should finally get fixed. this is known for a long time. you can also check this thread which is a year old
I posted it also in the coments for the EAP when it was released in late August 2020
Wow, that's ridiculous. With my previous laptop, I had been using the old stoplight version of the client which worked. This has to be fixed though.