Created on
‎10-02-2024
12:01 AM
Edited on
‎11-14-2025
03:23 AM
By
Jean-Philippe_P
| Description |
This article describes how to ensure the captive portal on Apple devices is working after performing the initial configuration from here: FortiAuthenticator as a Wireless Guest Portal for FortiGate. To verify whether the initial captive portal configuration is correct, test it on a Windows or Android device first. |
| Scope | FortiOS non-EOS versions. When Captive Portal authentication is used. |
| Solution |
The following Address Objects have to be created first.
DNS Object:
Captive.apple.com FQDN object:
There are extra steps required for Captive Portal authentication to work on Apple devices. These configuration steps have to be carried out on the FortiGate:
config firewall policy edit 26 set name "captive-portal-exempt" set srcintf "captiveportal" set dstintf "virtual-wan-link" "port4" set action accept set srcaddr "all" set dstaddr "google dns" "fac" "captive.apple.com" set schedule "always" set service "ALL" set logtraffic all set nat enable next end
config user setting unset auth-cert end
config user setting
By default, FortiGate also checks the client's MAC address when authenticating, and if the client is behind a router before reaching the firewall, the loopback behaviour. That setting above disables it. |
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.