Is there a way using the provisioning file to Give the Connection a more meaningful name?
At present it displays the FQDN it is using to connect with, once connected and you look at the "Connection Name" in "Monitor connection" it shows the FQDN that was provided in the .pro file.
We have tried putting the
"display_name": "My VPN",
In the .pro file but it doesn't work.
We can rename the connection once it's created but if you do an "Update Policy" the connection resets back to the FQDN.
We expected the "display_name" field to handle this but it doesn't
The issue seems to be introduced by the new Ipsec pushing. In fact the initial connection has the correct name. After going to click on connect, Sophos Connect will fetch the current conf of XG Firewall…
Thank you for reaching out to Sophos Community.
I'm in a discussion with the internal team with regards to reported behavior with the provisioning file. I'll try to import the provisioning file into the lab environment and will update this thread.
any news? , i have the same problem
The issue seems to be introduced by the new Ipsec pushing. In fact the initial connection has the correct name. After going to click on connect, Sophos Connect will fetch the current conf of XG Firewall, which is basically has the name from XG Firewall. See IPsec (remote access).
The provisioning file enables the Sophos Connect client to automatically import IPsec(.scx) and SSL VPN(.ovpn) configuration files through the user portal.
Sophos Connect imports .ovpn file as a separate profile, which does not have a provision to provide a connection name. It’ll have an IP address(Gateway) as a connection name to which it connects first.
"display_name" element is for provisioning file(.pro) which you import to Sophos Connect client.