Artica allows you to connect your Artica appliance with your Active Directory. The Active Directory feature require a valid Enterprise Edition.
The connection to the Active Directory can be done using 3 ways:
Using LDAP/LDAPs: Artica is able to use the LDAP protocol to retrieve and test credentials. Using this way, you are able to: - Manage Administrators and privileges on the Artica Web Console using your Active Directory database - Create dedicated rules based on Active Directory users/computers group for the RDS Proxy service
NTLM or Kerberos: The main benefit using the Active Directory is the “silent authentication” with Proxy Edition. If you plan to connect your Radius service, you need to use NTLM method It means when using the proxy, browser automatically sends the Windows session credentials to the proxy using NTLM or Kerberos method. In this case, the user did not have to put its credentials in a login box.
Silent authentication (identification without joining the domain): the proxy reads the Windows account name that the browser sends through NTLM, without verifying the password and without joining the appliance to the domain (no keytab, no winbind). The Active Directory groups of that account are then resolved through your LDAP connections, so your rules based on Active Directory groups keep working. Use it when joining the domain is not possible or not wanted (DMZ, branch offices, a domain you do not administer, a quick deployment), for logging, reporting and web filtering by group. Because the password is not checked, any client can claim any account name: do not use this method for security-sensitive access decisions. When the password must be validated, use Kerberos or NTLM instead.