EFW Support

Support => EFW SMTP, HTTP, SIP, FTP Proxy Support => Topic started by: scp on Wednesday 19 September 2012, 07:35:10 am



Title: ldap authentication problem
Post by: scp on Wednesday 19 September 2012, 07:35:10 am
I got a problem when trying to add an LDAP authentication profile for the proxy! I'm using a QNAP NAS as the LDAP server! The QNAP tells me this:

Server IP: 192.168.10.250
Domainname: qnap.local
Password: test
Root DN: cn=admin,dc=qnap,dc=local
User-DN: ou=people,dc=qnap,dc=local
Group-DN: ou=group,dc=qnap,dc=local

I've tried this configuration on my Endian 2.5.1 FW:

LDAP Server: 192.168.10.250
Bind DN Settings: cn=users,dc=qnap,dc=local
Bind DN Username: cn=admin,dc=qnap,dc=local
User object class: people
Group object class: group
LDAP Server port: 389
LDAP type: LDAP v3 server
Bind DN password: test

Is this configuration ok? When I try adding a custom access policy for the proxy and try to select authentication user-based, it says: can't find the ldap server

Thank's in advance for your help!!!


Title: Re: ldap authentication problem
Post by: dda on Thursday 20 September 2012, 11:07:14 pm
What OS are you using on the server.  I found Microsoft ADAM easiest to work with as there is no configuration, it connects to the directory automatically.


Title: Re: ldap authentication problem
Post by: scp on Thursday 20 September 2012, 11:33:17 pm
QNAP is a linux based operating system using OpenLDAP!


Title: Re: ldap authentication problem
Post by: arcclaro on Tuesday 23 October 2012, 03:46:06 am
QNAP is a linux based operating system using OpenLDAP!

scp,

I'm in the same situation...

Also have a QNAP unit, but unable to use it with Endian as LDAP server...


Any news? Do you already had success!?!!

thanks


Title: Re: ldap authentication problem
Post by: dda on Tuesday 23 October 2012, 09:08:18 am
Sorry i have never hear of it before. :-[
Did you try using an ldap browser?  That helped me to find the problem in my config.

I n my config this line ou=people,dc=qnap,dc=local is in Bind DN Settings.  Dunno if that helps.  you can look in the ldap browser to see what it should be, in my case it was ou="mybusiness",dc=mydomain,dc=mydomainsuffix.