We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda Web Security Service

Authentication with the Barracuda Web Security Service Connector

  • Last updated on

In this article:

The Barracuda Web Security Service Connector fully and transparently integrates with various user authentication technologies, including LDAP/AD, Novell’s eDirectory, NTLM, or Kerberos, authenticating users before tagging traffic. For LDAP/AD deployments, you can deploy a Domain Controller Agent with the Barracuda Web Security Service Connector to authenticate user identities.

If you deploy a Barracuda Web Security Service Connector to proxy traffic to the Barracuda Web Security Service for enforcement, you will need to configure users and groups on the Barracuda Web Security Service Manager so traffic can be matched to policies or reports configured for the user or group. Refer to How to Configure Authentication for details.

You can specify proxy and caching settings by selecting a Barracuda Web Security Service Connector from the list on the Configuration > Gateway page and selecting the Authentication tab. The Authentication tab allows you to choose and configure the following authentication mechanisms:

Choose only one authentication mechanism. The Barracuda Web Security Service Connector does not support authentication using more than one method.

LDAP Authentication Management

NTLM Authentication Management

Kerberos Authentication Management

Last updated on