Fortinet white logo
Fortinet white logo

FortiGate

FortiGate

Follow this procedure on the FortiGate GUI to configure captive portal.

  1. Navigate to User and Device > RADIUS Servers and create a new RADIUS server authentication profile. Select Create New.
  2. Enter the primary RADIUS server details. The Primary Server IP/Name - (Application server IP address). The Primary Server Secret should be the same as the RADIUS Secret Key configured on the FortiPresence VM GUI (Portal > Portal Settings > Radius Clients).
  3. Enter the NAS IP and click OK.
  4. Configure RADIUS server accounting profile via the FortiGate CLI mode. Run the following commands in the same order.
    config user radius
    edit <RADIUS profile created in Step 2>
    config accounting-server
    edit < integer>
    set status enable
    set server <IP address of the RADIUS server>
    set secret <same as the RADIUS Secret Key configured on the FortiPresence VM GUI (Portal > Portal Settings > Radius Clients)
  5. Navigate to User and Device > User Groups and create a new user group to map the RADIUS servers to the user group for ease of configuration. Select Create
  6. Click Add in the Remote Groups section and select the configured RADIUS authentication server. Click OK.
  7. Navigate to Policy and Objects > Addresses to create individual addresses for exemption FQDNs. Select Create New > Addresses and update the configuration parameters as required.
  8. Select Type as FQDN and enter the exempt FQDN. Click OK.
  9. Repeat Steps 7 and 8 to create exclusion based addresses for all FQDNs.
  10. Create address groups to easily map the individual FQDNs. Select Create New > Address Group and update the configuration parameters as required and populate the FQDN entries in the Members field. The FQDN entries are displayed in the right-side panel.

    You can create a single address group or multiple groups based on your requirement.
  11. Navigate to WiFi and Switch Controller > SSID to create an SSID. Click Create New > SSID and update the configuration parameters as required.
  12. Select the Security Mode as Captive Portal and the Authentication Portal type as External.
  13. Enter the Authentication Portal, (Captive Portal URL copied from the FortiPresence VM GUI – Portal Management > Radius Configuration) and select the created User Group.
  14. Select the address groups created for exempted FQDNs in Exempt Destination/Services. Click OK.
  15. Set the Redirect After Captive portal to Specific URL and specify https://<FortiPresence Connect FQDN>/portal/success. The actual redirect option can be specified while creating the portal on FortiPresence VM GUI - Adding a New portal
  16. Navigate to Policy & Objects > IPv4 Policy to configure Firewall policies. Select Create New.
    You are required to create the following three Firewall policies:
    1. Policy to allow access to the DHCP and DNS services before authentication.
    2. Policy to allow access to the exempted FQDNs for authentication.
    3. Policy to allow access to the internet after authentication.

    The following is an example of a policy to allow access to the exempted FQDNs for authentication.

FortiGate

FortiGate

Follow this procedure on the FortiGate GUI to configure captive portal.

  1. Navigate to User and Device > RADIUS Servers and create a new RADIUS server authentication profile. Select Create New.
  2. Enter the primary RADIUS server details. The Primary Server IP/Name - (Application server IP address). The Primary Server Secret should be the same as the RADIUS Secret Key configured on the FortiPresence VM GUI (Portal > Portal Settings > Radius Clients).
  3. Enter the NAS IP and click OK.
  4. Configure RADIUS server accounting profile via the FortiGate CLI mode. Run the following commands in the same order.
    config user radius
    edit <RADIUS profile created in Step 2>
    config accounting-server
    edit < integer>
    set status enable
    set server <IP address of the RADIUS server>
    set secret <same as the RADIUS Secret Key configured on the FortiPresence VM GUI (Portal > Portal Settings > Radius Clients)
  5. Navigate to User and Device > User Groups and create a new user group to map the RADIUS servers to the user group for ease of configuration. Select Create
  6. Click Add in the Remote Groups section and select the configured RADIUS authentication server. Click OK.
  7. Navigate to Policy and Objects > Addresses to create individual addresses for exemption FQDNs. Select Create New > Addresses and update the configuration parameters as required.
  8. Select Type as FQDN and enter the exempt FQDN. Click OK.
  9. Repeat Steps 7 and 8 to create exclusion based addresses for all FQDNs.
  10. Create address groups to easily map the individual FQDNs. Select Create New > Address Group and update the configuration parameters as required and populate the FQDN entries in the Members field. The FQDN entries are displayed in the right-side panel.

    You can create a single address group or multiple groups based on your requirement.
  11. Navigate to WiFi and Switch Controller > SSID to create an SSID. Click Create New > SSID and update the configuration parameters as required.
  12. Select the Security Mode as Captive Portal and the Authentication Portal type as External.
  13. Enter the Authentication Portal, (Captive Portal URL copied from the FortiPresence VM GUI – Portal Management > Radius Configuration) and select the created User Group.
  14. Select the address groups created for exempted FQDNs in Exempt Destination/Services. Click OK.
  15. Set the Redirect After Captive portal to Specific URL and specify https://<FortiPresence Connect FQDN>/portal/success. The actual redirect option can be specified while creating the portal on FortiPresence VM GUI - Adding a New portal
  16. Navigate to Policy & Objects > IPv4 Policy to configure Firewall policies. Select Create New.
    You are required to create the following three Firewall policies:
    1. Policy to allow access to the DHCP and DNS services before authentication.
    2. Policy to allow access to the exempted FQDNs for authentication.
    3. Policy to allow access to the internet after authentication.

    The following is an example of a policy to allow access to the exempted FQDNs for authentication.