A Portal Policy consists of one User/Host Profile and one Portal Configuration. The User/Host Profile is used to determine the hosts to which this policy might apply. The Portal Configuration controls the look and feel of the portal pages displayed to those users and hosts when they connect to the network and register. Portal Policies determine the portal assigned to a connecting host in an environment where there are multiple portals.
Portal Policies rely on a limited set of host information to match a Portal Configuration with a User/Host Profile. When an unregistered host connects to the network, there are only a few pieces of data that are known about the host and no data is known about the user. Therefore, the User/Host profile used in a Portal Policy can only use the connection location, the host IP Address, the host MAC Address or the Operating System to match a connecting host.
Portal Policies are ranked with 1 being the highest rank. When a host connects to the network, the policies are evaluated from the highest rank down until a matching policy is found. That policy is assigned to the host and the portal within the policy is displayed.
There may be more than one Portal Policy that is a match for this host/user, however, the first match found is the one that is used.
If you create a User/Host Profile with fields Where (Location) set to Any, Who/What by Group set to Any, Who/What by Attribute left blank and When set to always, it matches ALL users and hosts. This is essentially a Catch All profile. If this User/Host Profile is used in a policy, all policies below that policy are ignored when assigning a policy to a user or a host. To highlight this, policies below the policy with the catch all profile are grayed out and have a line through the data.
If a host does not match any of the policies listed, FortiNAC connects the host to the user-specified default portal. See Select a default portal.