?
Solved

Barracuda 300 Firewall and LDAP settings!

Posted on 2007-04-03
4
Medium Priority
?
3,747 Views
Last Modified: 2012-06-22
I have a Barracuda 300 Firewall and I need some help on setting up the Ldap setting for Windows 2003 AD/Exchange 2003.  Under the Domain tab -> Edit Ldap.  

One question what should I put for Bind DN:  I assume this is any valid users in AD or does it need to be a special user?  

Second question is LDAP UID?  The help indicates this should be the SAMaccountName.  Where do I located that name?
0
Comment
Question by:lwrogers
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
4 Comments
 
LVL 2

Expert Comment

by:Glowingdark
ID: 18848346
Hello,
   You should be able to use any account for bind dn.  We created an account called "lookup" and in our bind dn box we use "lookup@<domain.name>", substituting your real domain name for <domain.name>.  The bind password is the password for this account.  In LDAP UID we just have "uid".   LDAP primary email attribute is set to "email".

Kevin
0
 

Author Comment

by:lwrogers
ID: 18855381
What do you use for the Valid email address?  Also everything seems to be working now but I'm getting the following warning:
Warning: Uniquely identifying attribute 'uid' not found
0
 
LVL 2

Accepted Solution

by:
Glowingdark earned 2000 total points
ID: 18859885
In "Valid Email" I just have a valid email address for one of our users.  When I press "test LDAP" I actually get the warning about uid not being valid also, but the ldap lookup works.  I incorrectly stated above that our  LDAP primary email attribute was "email", it is actually not, it is "mail".  

Below are the results I get when I press test ldap:

Found address validaddress@mydomaindomain.com in 0.67 seconds.
Warning: Uniquely identifying attribute 'uid' not found. Primary e-mail alias attribute 'mail' has value of validaddress@mydomain.com.

0
 

Expert Comment

by:TransitionalData
ID: 21471772
lwrogers,
You want to use "SAMaccountName" as the LDAP UID.  this distinguishes that each user is identified by their unique username.  UID is not one of the LDAP fields within AD and thats why the warning comes up.
0

Featured Post

Ransomware-A Revenue Bonanza for Service Providers

Ransomware – malware that gets on your customers’ computers, encrypts their data, and extorts a hefty ransom for the decryption keys – is a surging new threat.  The purpose of this eBook is to educate the reader about ransomware attacks.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Compliance and data security require steps be taken to prevent unauthorized users from copying data.  Here's one method to prevent data theft via USB drives (and writable optical media).
New style of hardware planning for Microsoft Exchange server.
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …
Are you ready to implement Active Directory best practices without reading 300+ pages? You're in luck. In this webinar hosted by Skyport Systems, you gain insight into Microsoft's latest comprehensive guide, with tips on the best and easiest way…
Suggested Courses
Course of the Month13 days, 8 hours left to enroll

801 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question