Sophos Connect 2.0 SSLVPN username with spaces

Hi Bart van der Horst,

Thank you for reaching out to the Community! 

Are you having an issue with the local users or AD users? 

I have tried to replicate your issue with a local user with space in the user name, but It works for me. I have tested this on SFOS v17.5 MR14 and v18.0.1 GA. 

I would advise you to replicate the issue and collect access_server logs in debugging and send me the logs via PM. 

Command to put the access_server in debug: service access_server:debug -ds nosync

You could run the same command to remove the service from debugging.  

Thanks,

Hello,

Tested with space in "user name" as shown in quotes and the SSL VPN connection is established successfully.

Is the user using the provisioning file to download the connection file? If yes, then if the user has already provisioned the connection then ask the user to clear credentials and then update policy from the settings menu on that connection as shown below.

Please let us know the results.

Ramesh

Hi H_Patel,

Thanks for the reply, this with a ad user, userportal and sophos connect ipsec is doing fine only sslvpn with the new sophos connect is doing this, it sees only the first part of the username until the space.

I inherited this network/customer, else i never allowd usernames with spaces. But it is wat it is i think.

Thanks. 

Hi, old sslvpn client was working, only sslvpn with Sophos connect client is not, user can connect to userportal and ipsec.

Bart,

What is the user name configured as? Are you using the ovpn file or are you using a provisioning file? I need to configure the user name exactly like you have and try it again. 

Ramesh

Hi Ramesh, the vpn is using a provisioning file. Username is like "bart van der horst", only "bart" is seen in the logs as: failed, and that is correct as there is no "bart".

Thanks

Bart,

I have verified that if the user name has a single space (for ex: bart van) then it works. But if it has multiple names like in your case then it fails. Will log this as a bug and fix in SC 2.1 release. Sorry for the inconvenience.

Ramesh

Thanks Ramesh.

It's also not working with a blank/space in password. (at least the EAP had this issue)