[prev in list] [next in list] [prev in thread] [next in thread] 

List:       imp
Subject:    Re: [horde] Possible Bug in LDAP Auth
From:       Jan Schneider <jan () horde ! org>
Date:       2016-12-20 9:05:05
Message-ID: 20161220090505.Horde.tave-TvJnO3rNS11mk_lAhQ () neo ! wg ! de
[Download RAW message or body]

Please don't top-post.

Zitat von roellig@roellig-ltd.de:

> Quoting Jan Schneider <jan@horde.org>:
>
>> Zitat von roellig@roellig-ltd.de:
>>
>>> Hi,
>>> the last Update from Horde is killing the LDAP auth.
>>
>> What do you consider the "last update"? Which packages did you  
>> update, and from which version?
> hi,
>
> from horde 5.2.11 to 5.2.12, am not sure if this is really correct
> but that is still so.

There haven't been any LDAP related changes between these versions.  
You either must have updated other packages too, or this is not  
related to the versions at all, but rather to your personal upgrade  
method.

>>> In the config => LDAP is the $conf[ldap][user][objectclass] = *
>>>
>>> And this block the Login. In the ldap log i see the
>>> serach filter ist (&(objectclass=/A2)(uid=blauser)
>>>
>>> i have change vom * to shadowAccount an the LDAP Login is running.
>>>
>>> Sorry for my english


-- 
Jan Schneider
The Horde Project
https://www.horde.org/

-- 
Horde mailing list
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: horde-unsubscribe@lists.horde.org
[prev in list] [next in list] [prev in thread] [next in thread]