On 05/20/2010 10:36 PM, Martin Rabl wrote:
Hi,
short question: the LDAP-Filter of SOGoUserSources ("filter" called) have not to be
filled with a real LDAP filter like (&(memberOF=CN=sogouser,CN=Users)(uid*)) ?
Shouldn't that be (&(memberOF=CN=sogouser,CN=Users)(uid=*)) ?
Also, is CN=Users your full base search?
What I saw in debug-logs (LDAP-Debugging on), the filter will be appended to
the user login (with an AND!?), so an user can not login, when the filter is
... erm ... damaged.
So I think, the filter has to be written in a SQL-like way?
Today I tried to connect SOGo on our companies Active Directory - runs good,
login is possible - but only without the filter.
First we tried
(&(objectClass=organizationalPerson)
(memberOf=CN=GroupwareAccounts,CN=Users,DC=securenet,DC=de)
(sAMAccountName=*))
does not run, but (objectClass=organizationalPerson) does.
Could it be possible that AD doesn't allow you to query sAMAccountName=* ?
Any usefull debugging info on the LDAP (AD) server ?
UIDFieldName is sAMAccountName, bindFields, too.
Thank you!
Martin
R's,
Hugo Monteiro.
--
fct.unl.pt:~# cat .signature
Hugo Monteiro
Email : [email protected]
Telefone : +351 212948300 Ext.15307
Web : http://hmonteiro.net
Divisão de Informática
Faculdade de Ciências e Tecnologia da
Universidade Nova de Lisboa
Quinta da Torre 2829-516 Caparica Portugal
Telefone: +351 212948596 Fax: +351 212948548
www.fct.unl.pt [email protected]
fct.unl.pt:~# _
--
[email protected]
https://inverse.ca/sogo/lists
