Displaying 2 results from an estimated 2 matches for "db_ldap_result_iterate_next_all".
2008 Mar 14
1
Bug in db-ldap.c with Dovecot1.1rc3
...ap.conf" snippet:
user_attrs =
homeDirectory=home,uidNumber=uid,gidNumber=gid,quotaKb=quota_rule=*:storage=%$
And this example LDAP entry:
dn: uid=testuser,ou=people,dc=domain.com
uid: testuser
homeDirectory: /mail/testuser
gidNumber: 100
cn: testuser
quotaKb: 20480
uidNumber: 121212
When db_ldap_result_iterate_next_all() runs, "quotaKb" is encountered,
which causes "ctx->template" to be set.
On the next iteration, "uidNumber" is encountered, but "ctx->template"
is still set, causing the "uid" value to be prepended with "*:storage=".
This is ref...
2007 Jul 25
1
v1.1 alpha1: can't pop/imap login with LDAP
...ap_result_iterate_context *ldap_iter;
const char *name, *const *values;
+ auth_request_init_userdb_reply(auth_request);
+
ldap_iter = db_ldap_result_iterate_init(conn, entry, auth_request,
conn->user_attr_map);
while (db_ldap_result_iterate_next_all(ldap_iter, &name, &values)) {
With the modification, LDAP authentication is working without any problem,
at least for our system.
However we are not sure whether the above modification affect other
functions of dovecot.
Is there an official patch to fix the problem already released? And
so...