Additional Notes

Additional Notes

This section describes some generic guidelines/information to using FortiPresence.

Any create and delete operation can take up to a maximum of 3 minutes to be visible on the FortiPresence GUI.
For setups involving multiple devices (FortiWLC/FortiGate) behind the NAT sharing the same public IP address, you are required to create a RADIUS client entry for each device type on the FortiPresence GUI.
For existing portals or new ones, you are required to mandatorily add the FQDN, presence-corp-prod-resource.s3.eu-west-1.amazonaws.com to the captive portal exemption list on the enforcement devices (FortiGate, FortiLAN Cloud, FortiWLC).
FortiWLC: The FortiWLC SSID must be configured in the tunnel mode; SSIDs in the bridge mode are NOT supported for Captive Portals.

FortiGate/FortiLAN Cloud: While configuring settings on SSID, set the Redirect URL to Specific URL and configure https://connect.presence.fortinet.com/portal/success as the URL. This is required for FortiPresence to register the device and user details. FortiPresence Portal Management provides options to set redirect after authentication to Original Request URL, Specific URL, or Default Success Page.
FortiGate: The supported authentication methods for FortiPresence are PAP, MS-CHAP, MS-CHAP-v2.
FortiPresence is General Data Protection Regulation (GDPR) compliant.

MAC addresses are not stored in FortiPresence; each visitor is referred by a unique User Key.
Personal details are not stored without the visitor’s consent - While logging on to FortiPresence, the visitor is presented with clear information about personal details being collected from the social network logins. Personal details, such as, name, gender, age, email etc. are stored only if the visitor gives an explicit consent, else such information is not stored.

Additional Notes

This section describes some generic guidelines/information to using FortiPresence.

Any create and delete operation can take up to a maximum of 3 minutes to be visible on the FortiPresence GUI.

For setups involving multiple devices (FortiWLC/FortiGate) behind the NAT sharing the same public IP address, you are required to create a RADIUS client entry for each device type on the FortiPresence GUI.

For existing portals or new ones, you are required to mandatorily add the FQDN, presence-corp-prod-resource.s3.eu-west-1.amazonaws.com to the captive portal exemption list on the enforcement devices (FortiGate, FortiLAN Cloud, FortiWLC).

FortiWLC: The FortiWLC SSID must be configured in the tunnel mode; SSIDs in the bridge mode are NOT supported for Captive Portals.

FortiGate/FortiLAN Cloud: While configuring settings on SSID, set the Redirect URL to Specific URL and configure https://connect.presence.fortinet.com/portal/success as the URL. This is required for FortiPresence to register the device and user details. FortiPresence Portal Management provides options to set redirect after authentication to Original Request URL, Specific URL, or Default Success Page.

FortiGate: The supported authentication methods for FortiPresence are PAP, MS-CHAP, MS-CHAP-v2.

FortiPresence is General Data Protection Regulation (GDPR) compliant.

MAC addresses are not stored in FortiPresence; each visitor is referred by a unique User Key.

Personal details are not stored without the visitor’s consent - While logging on to FortiPresence, the visitor is presented with clear information about personal details being collected from the social network logins. Personal details, such as, name, gender, age, email etc. are stored only if the visitor gives an explicit consent, else such information is not stored.

FortiPresence Cloud Release Notes

Additional Notes

Additional Notes