When firewall policy authentication is enabled, only traffic on supported protocols will trigger an authentication challenge. Select all supported protocols from the following:

SMTP (email) traffic is generally not subjected to direct firewall policy authentication challenges, as it typically operates between servers or from clients through email clients.

SSH (secure shell) is usually authenticated by the SSH server itself, not by an intermediate firewall policy directly challenging the user connection.

HTTP is a widely supported protocol for firewall policy authentication, often used with captive portals or explicit web proxy authentication.

FTP is another protocol that can trigger authentication challenges in firewall policies, especially for file transfer access control.

SCP (secure copy protocol) is a file transfer protocol over SSH and is authenticated by the SSH server, not typically by a firewall policy challenge.