Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 2 subscribers
  • Views 1689 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

LDAP with eDirectory

danitaz
I'm trying to provide LDAP access through ASG via eDirectory on an OES Linux server.  LDAP works fine with SQUID, so I know that it "should" work, but I'm having trouble with Astaro.

Here's what I have:

I have an internal network definition of:

Biggar 192.168.100.236

I have tried to setup LDAP authentication as follows:

 
Server: Biggar

Port: 363
User Attribute: UID or Common Name
Bind User DN: cn=user,o=cnc
Bind User Password: password
Base DN: o=cnc


I've tried both the UID and the Common Name as the user attribute.  I've tried both SSL and non-SSL.  I've tried with and without a bind user.

Squid just has:

auth_param basic program /usr/sbin/squid_ldap_auth -b "o=cnc" -f "uid=%s" -h 192.168.100.236:389

and it works fine, so I simply can't figure out what I've got wrong here.

Any assistance appreciated.

Thanks.

Danita


This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to QBNCGAR
    While I would have been happy to have done something quite that dumb, alas, no - it's just a typo!  I'm not sure where my brain was - but it wasn't talking properly to my fingers undoubtedly!

    Danita
  • 0 in reply to danitaz
    Okay - so I've done some more testing.  If I ssh over to the Astaro box and try to telnet to port 389 of my OES Linux server it just times out.  I can telnet to 389 from anywhere else on the network!  So what is blocking port 389 between Astaro and this box?  Astaro can ping that IP address, just can't telnet to the LDAP port!

    Thanks.

    Danita
  • 0 in reply to danitaz
    Oh for Pete's sake .  You have to create an ALLOW PACKET FILTER from the Astaro box to the the internal LDAP server.  I didn't see this anywhere in the docs, and just assumed that "internal" traffic was all allowed.

    So, now I can telnet to the LDAP server from the Astaro box.  I still can't get the authentication to work, but maybe now with the help of ndstrace I can figure out what's going on!

    Thanks.

    Danita
  • 0 in reply to danitaz
    You shouldn't have had to create a packet filter manually; I've seen other instances of having to manually open ports that the system is supposed to handle automatically...

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.

  • 0 in reply to BrucekConvergent
    Yeah - it finally struck me too that the log entry I saw earlier when trying to deal with an DNS entry was a blocked packet from the Astaro box to my internal DNS server.  It seemed "backwards" to me, and now I know why.  I think I had totally misconfired the DNS stuff anyway, because I had listed my DNS server as a "forwarder", so every time someone was wanting to do a DNS query the Astaro box was trying to hit my internal DNS server and couldn't.  

    I'm getting there [:)] - as with all things a bit of a learning curve to do new things!

    Danita
Cookie Information Banner