Objects : Objects > Authentication

Objects > Authentication
An authentication enforcement object specifies the method and service to use for authenticating end users who access your network resources. You assign the object to Authentication policy rules, which invoke the authentication method and service when traffic matches a rule (see Policies > Authentication).
The firewall has the following predefined, read-only authentication enforcement objects:
•
default-browser-challenge—The firewall transparently obtains user authentication credentials. If you select this action, you must enable Kerberos Single Sign-On (SSO) or NT LAN Manager (NTLM) authentication when you configure Authentication Portal. If Kerberos SSO authentication fails, the firewall falls back to NTLM authentication. If you did not configure NTLM, or NTLM authentication fails, the firewall falls back to the authentication method specified in the predefined default-web-form object.
•
default-web-form—To authenticate users, the firewall uses the certificate profile or authentication profile you specified when configuring Authentication Portal. If you specified an authentication profile, the firewall ignores any Kerberos SSO settings in the profile and presents an Authentication Portal page for the user to enter authentication credentials.
•
default-no-captive-portal—The firewall evaluates Security policy without authenticating users.
Before creating a custom authentication enforcement object:
•
•
To create a custom authentication enforcement object, click Add and complete the following fields:
Shared (Panorama only)
Disable override (Panorama only)
•
browser-challenge—The firewall transparently obtains user authentication credentials. If you select this action, the Authentication Profile you select must have Kerberos SSO enabled.
•
web-form—To authenticate users, the firewall uses the certificate profile you specified when configuring Authentication Portal or the Authentication Profile you select in the authentication enforcement object. If you select an Authentication Profile, the firewall ignores any Kerberos SSO settings in the profile and presents an Authentication Portal page for the user to enter authentication credentials.
•
no-captive-portal—The firewall evaluates Security policy without authenticating users.
Note: 
*
The firewall displays the Authentication Portal Comfort Page only for the first authentication challenge (factor), which you define in the Authentication tab of the Authentication Profile (see Device > Authentication Profile). For multi-factor authentication (MFA) challenges that you define in the Factors tab of the profile, the firewall displays the MFA Login Page.
Objects