[Owncloud] WG: LDAP login fails with latest git branch
Gronies, Thomas
Gronies at uni-wuppertal.de
Tue May 8 12:39:06 UTC 2012
Sorry Dirk, I just clicked on Reply without an eye on the recipient ;-)
Here it is for the list.
-----Ursprüngliche Nachricht-----
Von: Gronies, Thomas
Gesendet: Dienstag, 8. Mai 2012 14:03
An: 'Dirk Kastens'
Betreff: AW: [Owncloud] LDAP login fails with latest git branch
Hi,
I'm using Debian stable. In my /etc/ldap/ldap.conf BASE and URI have been commented out. Setting the correct configuration didn't solve the problem. Also, I did a tcpdump of the network interface and there was no LDAP traffic, when I tried to login.
After that I updated to the latest branch. Now it works.
Regards,
Thomas
-----Ursprüngliche Nachricht-----
Von: owncloud-bounces at kde.org [mailto:owncloud-bounces at kde.org] Im Auftrag von Dirk Kastens
Gesendet: Dienstag, 8. Mai 2012 11:00
An: owncloud at kde.org
Betreff: Re: [Owncloud] LDAP login fails with latest git branch
Hi,
>> When I try to login, OC uses the search base "dc=example,dc=com".
>> This is definitely a bug.
> I will check this.
>
>> When I leave the user and group trees empty, OC doesn't contact the
>> ldap server at all.
> The backend should use the standard base dn instead, probably setting
> it back to blank fails. I will check this as well.
I found out, that OC uses the ldap configuration that is defined in /etc/ldap.conf. It ignores the base setting of the ldap user app. In my ldap.conf the base setting was "dc=example,dc=com", so OC tries to find the user in this ldap tree. When I edit /etc/ldap.conf, so that it contains the correct base dn, OC can authenticate the user.
Regards,
Dirk
More information about the Owncloud
mailing list