You can globally enable Active Directory
authentication for users accessing web resources, for users accessing the
Deep Discovery Web
Inspector web console, for policy and HTTPS
inspection policy matches, and for account management.
You should consider the following when using Active Directory authentication for
Captive Portal:
-
If Deep Discovery Web
Inspector can do
pass-through authentication for the user requesting access to web resources,
a separate log on is not required.
-
If Deep Discovery Web
Inspector is unable to
transparently perform pass-through authentication, Captive Portal takes over
and authenticates the user. The Captive Portal sign-on page requires users
to specify a user name and password before accessing the network or
Internet.
The Captive Portal sign-on page takes over and authenticates for
the following reasons:
-
The primary reason why the Captive Portal page is shown is because
NTLM/Kerberos/basic authentication failed
|
Note
Only proxy mode supports basic authentication. Bridge mode does
not support basic authentication
|
-
The client computer is not added into an Active
Directory domain and the user name/password entered into Windows
authentication window is incorrect.
-
The keytab file for the domain is imported, which makes
this a Kerberos authentication scenario, and the time gap between
client and Deep Discovery Web
Inspector/KDC is too
large (by default the gap must be less than 5 minutes). If the time
gap is greater than five minutes, Kerberos authentication fails.
-
For some browsers in certain operating systems (for
example Firefox in Ubuntu) or because of incompatibility problems
with WIN2012R2, NTLM authentication might fail. Under these
circumstances, the Captive Portal page is shown.