Technical Tip: 'Access Denied' error while session-based authentication with explicit web proxy
| Description | This article describes why the end-user was facing an error of 'Access Denied', when FortiGate runs as an explicit web proxy with session-based authentication. |
| Scope | FortiGate v7.4+. |
| Solution | When FortiGate runs as an explicit web proxy with session-based authentication, with a typical configuration below, end-users can access most websites except *.microsoft.com:
This could be because the wildcard FQDN object 'microsoft' is exempted.
With session-based authentication, SSL/TLS deep inspection is required. However, if there is an object configured under the SSL exemption list, the session-based authentication is skipped. Then the end user got an error of 'Access Denied'.
Therefore, the solution is to remove the relevant object under 'Exempt from SSL Inspection' from the SSL/SSH inspection profile being used. |