This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sophos Connect 2.0 SSLVPN username with spaces

Hi,

I've got a customer with XG210 and firmware 18.0.1, now with the new Sophos Connect i want to migrate all the users to SC.

Some of those users have spaces in there username, the SSLVPN seems to not accept them.

Logs says:

SSL VPN Authentication

Failed

***

83.247.65.80

N/A

AD,Local

User **** failed to login to SSLVPN through AD,Local authentication mechanism because of wrong credentials

When connecting through IPsec:

Firewall Authentication

Successful

bart van der horst@****.local

10.81.225.6

IPSec

User bart van der horst@**.local of group Remote Desktop Server Users logged in successfully to Firewall through authentication mechanism from 10.81.225.6

Logging in to the userportal, also no problem.

Is this a known bug, and will it be resolved?

Thanks,

Bart van der Horst

This thread was automatically locked due to age.

Top Replies

rmk_2018 over 4 years ago +2

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…

Parents

0 rmk_2018 over 4 years ago

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
Cancel
Vote Up +2 Vote Down

Cancel
0 Bart van der Horst over 4 years ago in reply to rmk_2018

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

Bart van der Horst

Sophos XG v18-v21 Certified Architect
Cancel
Vote Up 0 Vote Down

Cancel
0 rmk_2018 over 4 years ago in reply to Bart van der Horst

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
Cancel
Vote Up +1 Vote Down

Cancel

Reply

0 rmk_2018 over 4 years ago in reply to Bart van der Horst

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
Cancel
Vote Up +1 Vote Down

Cancel

Children

0 Bart van der Horst over 4 years ago in reply to rmk_2018

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 van der Horst

Sophos XG v18-v21 Certified Architect
Cancel
Vote Up +1 Vote Down

Cancel
+1 rmk_2018 over 4 years ago in reply to Bart van der Horst

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
Cancel
Vote Up +2 Vote Down

Cancel
0 Bart van der Horst over 4 years ago in reply to rmk_2018

Thanks Ramesh.

Bart van der Horst

Sophos XG v18-v21 Certified Architect
Cancel
Vote Up +1 Vote Down

Cancel
0 LHerzog_Central over 4 years ago in reply to Bart van der Horst

It's also not working with a blank/space in password. (at least the EAP had this issue)
Cancel
Vote Up +1 Vote Down

Cancel