Extra options for sophos connect VPN client

Hello Eduardo Diaz Comellas,

Thank you for reaching out to the community, may we know what is the SFOS version and what is the Sophos Connect client version you are using?
You may refer the Sophos Connect provisioning file: https://docs.sophos.com/nsg/sophos-firewall/19.0/Help/en-us/webhelp/onlinehelp/AdministratorHelp/RemoteAccessVPN/IPsecSSL/SophosConnect/RAVPNSConProvisioningFile/index.html

Any new information about this?

The Sophos Connect provisioning file didn't help. I think it would be quite easy to add this option to the vpn client.

so you want to add various user profiles in the sophos connect client ?

Either have several profiles (as it was possible with the old SSL client) and let the user chose, or just download the profile every time.  Both would be good solutions for my use case.

Right now, if you want to change the user of a VPN you need to take a lot of steps. This is inconvenient for shared computers

Well ssl vpn profiles you can download from the user portal and you can import the profiles as per the screenshot below:

That approach wont work if the connection is to the same firewall. Let me elaborate:

- I created a profile file. I distribute this profile file to the users (BTW, it would be great if we could "upload" the profile to the firewall's user portal)

- They import it in Sophos Connect and, when they connect for the first time, they are asked for a login/password/capcha. Everything is OK so far.

- After a successful connection, the specific user used for the first connection is cached. You won't be able to connect using other credentials (login/password)

- If you want to connect as other user, you have to remove the connection from Sophos Connect and import the profile again.

- If you try to import the connection twice, so two users can connect using their own credentials, you get an error stating that the connection already exists.

We have laptops that are used by field workers, assigned each day randomly. I would want to avoid the end users to go through all the process of deleting the profile, importing a new one and connecting.

Any suggested workaround?

That approach wont work if the connection is to the same firewall. Let me elaborate:

- I created a profile file. I distribute this profile file to the users (BTW, it would be great if we could "upload" the profile to the firewall's user portal)

- They import it in Sophos Connect and, when they connect for the first time, they are asked for a login/password/capcha. Everything is OK so far.

- After a successful connection, the specific user used for the first connection is cached. You won't be able to connect using other credentials (login/password)

- If you want to connect as other user, you have to remove the connection from Sophos Connect and import the profile again.

- If you try to import the connection twice, so two users can connect using their own credentials, you get an error stating that the connection already exists.

We have laptops that are used by field workers, assigned each day randomly. I would want to avoid the end users to go through all the process of deleting the profile, importing a new one and connecting.

Any suggested workaround?

Well I am not sure, the following can be relatable or not ?
as there is one re-naming an existing connection is in development - NCL-1686.
That way it will provide an ability to Import connection via provisioning over an renamed existing connection to the same gateway. Which is again planned to be fixed in Sophos Connect 2.3. 

Oh, I can see. That would be helpful.

I would suggest to add an option in the provisioning file to "Not store user configuration" and force the download of a fresh user configuration every time (as if the profile had just been imported)

Thanks.

Yup, will pass on the information to dev on this !! 

Is there anywhere I can check that feature request? ideas.sophos.com is retired now.

Thanks for your help.

The ideas portal is retired now: https://community.sophos.com/b/community-blog/posts/sophos-ideas-portal-retirement 
---------
The context "known" which I used in the previous comment is that the Sophos team has received instances and working on it. 
The known issue list to which you are referring is the list of ID which has been marked as in known behavior or Known issues.
Which can be found under the KBA - https://support.sophos.com/support/s/article/KB-000036055?language=en_US
---------
For this NCL ID details, you will not be able to see in that product known issue list and will be able to see in the release note of that Sophos Connect Client in which fix will be taken. 

Hi Eduardo Diaz Comellas,

We will relay your feature request to your Account Manager this time, but going forward as per the new Feature Request Process you may reach out to your Account Manager directly so they can input into our system.

https://community.sophos.com/sophos-xg-firewall/f/discussions/136558/uploading-a-sophos-connect-vpn-profile-to-the-user-portal DELETED as a duplicated of this thread