If a guest user with an unmanaged device is redirected to authenticate against the captive portal,
the clients browser is pointed to the first IP address of the firewall.
Like 172.16.16.16:8090/httpclient.html URL]
The hostname or a configurable name should be used for the redirection to match with
a public trusted certificate.
This is very important n environments were the accessing clients cannot be controlled
and the user should not be confronted with an certificate error.
Is there a plan to fix that? If yes, when?
Same issue, please vote ideas.sophos.com/.../11580213-captive-portal-fqdn-support
Guys, I found a workaround for this. It's working for me.
My box XG450 (SFOS 17.0.5 MR-5)
That's it enjoy. Ensure you have a valid HTTPS certificate uploaded to the UTM. Above method is working for me