Description |
This article describes how to restrict access to a personal Gmail Account and allow access to Specific Domains' Google Email accounts. |
Scope | FortiGate. |
Solution |
Requirement: FortiGate must be in Proxy-based SSL Deep Inspection mode. A web-proxy profile must be attached to the FortiGate policy where domain restrictions are to be applied. Without the Web-proxy profile, the X-GoogApps-Allowed-Domains header will not be injected, and personal Gmail accounts will not be blocked. Google-related domains must not be exempted from SSL/SSH inspection in the Custom Deep Inspection profile. Explanation: Exempting Google domains from deep inspection prevents FortiGate from decrypting the traffic. If traffic is not decrypted, FortiGate cannot inject the header to enforce allowed domains.
How it works: The firewall will inject the HTTP header X-GoogApps-Allowed-Domains. It is also possible to inject multiple domains via the X-GoogApps-Allowed-Domains header.
Firewall Configuration: Follow the instructions in Technical Tip: Restrict Google account usage to specific domains.
Once configured, set up the specific email domains in the Web-Filter. Configuration on the CLI is injected by the firewall.
config web-proxy profile edit "Auto-web-proxy-profile_iwd4cg3tf" config headers edit 1 set name "X-GoogApps-Allowed-Domains" set content "abc.com, xyz.com" <----- The company domain is hosted in Google Mail services. next end next end
end
1. Remove all Google-related accounts under Exempt from SSL Inspection.
|
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.