Ensured captive portal for unauthenticated users who use HTTP/HTTPS browsers

You can ensure that an unauthenticated user who issues an access request using an HTTP/HTTPS browser is presented with a captive portal interface to allow them to authenticate. It can happen that non-browser HTTP/HTTPS services running in the background at the same time can trigger captive portal authentication creating a race condition that suppresses presentation of the captive portal interface to the browser user. You specify the auth-only-browser parameter for firewall-authentication in security policies to direct it to ignore non-browser HTTP/HTTPS requests. You can also configure the auth-user-agent parameter to direct firewall authentication to check the User-Agent field in the browser header for information identifying content, such as Opera.