I am getting some strange behavior from the UTM running hte 9.192-8 firmware. In order to accomplish a request from a client, I had to enable HTTPS Decrypt and Scan filtering. I was getting certificate errors related to the UTM not being a Trust Root Authority, so I instlled the cert from the UTM as a trusted authority, andthat error went away. However, the new error I am getting indicates that certificates now have "Mismatched Names". After reviewing the certificates, the UTM is reissuing the certificates to the IP address of the requested site instead of the URL. If I input the IP address it issued the cert for, I get no certificate errors. I have attached some screenshots to show the issue.
I'm going to add and say I'm having the same sorts of issues.
The scenario is.
I'm using 9.192-8. Web protection is in Transparent AD-SSO mode.
Internal DNS is configured correctly. The FQDN on the UTM has been added to the Intranet Sites as a trusted entity.
AD-SSO works very well!
When enabling the "SSL Traffic - URL Filtering Only" and then visiting a HTTP site and then an SSL site, all works as expected.
The issue i'm having, which is very similar to above, is when I open my browser and browse to an SSL site first up. Typically my home page is Google.com.au; which i've opted in to force an SSL connection.
At this point, I get a certificate warning that the UTM has injected it's own SSL decryption certificate into the request of which the browser is receiving, I don't think this should be happening.
Why it selectively happens between using plain HTTP prior to going to an SSL site is beyond me.
I'm going to add and say I'm having the same sorts of issues.
The scenario is.
I'm using 9.192-8. Web protection is in Transparent AD-SSO mode.
Internal DNS is configured correctly. The FQDN on the UTM has been added to the Intranet Sites as a trusted entity.
AD-SSO works very well!
When enabling the "SSL Traffic - URL Filtering Only" and then visiting a HTTP site and then an SSL site, all works as expected.
The issue i'm having, which is very similar to above, is when I open my browser and browse to an SSL site first up. Typically my home page is Google.com.au; which i've opted in to force an SSL connection.
At this point, I get a certificate warning that the UTM has injected it's own SSL decryption certificate into the request of which the browser is receiving, I don't think this should be happening.
Why it selectively happens between using plain HTTP prior to going to an SSL site is beyond me.
