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 NextGen Firewall X


This Product is Going End-of-Life and End-Of-Support

End-Of-Sales: As of December 1st, 2018, all new sales for Barracuda NextGen Firewall X Series products have ceased. Only renewals of software and hardware subscriptions for a maximum of one year are available for a limited time up to an expiration date of 30th November 2020.

End-Of-Life and End-Of-Support on December 1st 2020: All Barracuda Firewall X-Series sales will cease; neither new sales nor any renewals will be available. If you currently hold a maintenance and support contract, you will continue to receive our award-winning support and services until your contract expires, or until Dec 1st, 2020, whichever occurs first. Please see the End-Of-Life definition as described in the End of Support and End of Life Information.

How to Configure MSAD Authentication

  • Last updated on

Configure the Barracuda NextGen Firewall X-Series to allow authentication and authorization of domain users on a Microsoft Active Directory (MSAD) server. To reduce load querying for large environments, you can also filter unwanted group membership information by creating group filter patterns.

Configure MSAD Authentication

Connect the X-Series Firewall with your Microsoft Active Directory (MSAD) server and configure MSAD as external authentication scheme. 

  1. Go to the USERS > External Authentication page.
  2. Click the Active Directory tab.
  3. In the Basic section, click Add. 
  4. Enter the Domain Controller IP address.
  5. In the Searching User field, enter the MSAD Searching User in the user@domain format:

    Do not use the domain\user format.
  6. Enter the Searching User Password.
  7. Specify the Base DN where the lookup should be started. E.g., CN=trainee,OU=sales,DC=mycompany,DC=com

    Do not use spaces between the entries.
  8. Set Cache MSAD Groups to Yes to reduce network traffic and server load on the domain controller.
  9. Select Use SSL if your Active Directory server is configured to use SSL.
  10. (Optional) Select Follow Referrals to use Active Directory's global catalog and follow the referrals. When a requested object exists in the directory but is not present on the contacted domain controller, the referral gives the client a location that holds the object or is more likely to hold the object. It is also possible for the referred-to domain controller to refer to a next hop location. The number of next hops is defined in Maximum Hops for Referrals.

  11. Click Save
  12. (Optional) Add Group Filter Patterns to filter unwanted group information. Wlldcards are allowed.
    Example: When using pattern: *SSL*, and the following group membership strings are used:
    User01 group membership string: CN=xyz,OU=sales,DC=mycompany,DC=com
    User02 group membership string: CN=SSL,DC=mycompany,DC=com
     Only User02 will match.
  13. Click Save.

The configuration is now added to the EXISTING AUTHENTICATION SERVICES table and you can use the MSAD authentication service on the X-Series Firewall.



To test, if the connection is working, try to login as the user from another network host. When a user, for whom the authentication scheme applies, logs into the network, a log entry is created showing the login details such as source address, success or failure, time, etc. To access authentication logs, go to the LOGS > Authentication Logs page.

If the connection cannot be established:

  • Make sure that you have entered the MSAD searching user in the Searching User field in the correct format: user@domain. Do not use the domain\user format.
  • Verify that the entry for the Base DN where the lookup should be started does not contain spaces. 
  • Check the Logs > Authentication Log page for error messages when connecting to your Active Directory server.
Last updated on