search for: auth_passdb_lookup

...> > curious if there's a better way. I tried various quoting without success. > > Didn't try escaping yet. > > > > > > 2) Instead of string, return a key value table. you can have spaces in > > values. > > > > > > > Does this work for auth_passdb_lookup too, or just auth_userdb_lookup? I've > been returning a table with auth_userdb_lookup just fine. But when I try > using it with passdb (and despite being very very sure that a 'password' > key exists in the table I'm returning from auth_passdb_lookup() -- I'm > logg...

...t; > > > Didn't try escaping yet. > > > > > > > > > > > > 2) Instead of string, return a key value table. you can have spaces in > > > > values. > > > > > > > > > > > > > > > Does this work for auth_passdb_lookup too, or just auth_userdb_lookup? > > I've > > > been returning a table with auth_userdb_lookup just fine. But when I try > > > using it with passdb (and despite being very very sure that a 'password' > > > key exists in the table I'm returning from a...

...ase/Lua >> >> Any words of wisdom on using it? I'd be putting a bunch of mysql logic in >> it. Any horrible gotchas there? When it says 'blocking', should I assume >> that means that a auth worker process will *not* accept any new auth >> lookups until both auth_passdb_lookup() and auth_userdb_lookup() have >> completed (in which I'd be doing several mysql calls)? If that's the case, >> I assume that the number of auth workers should be bumped up. >> >> And is a 2.3 release fairly imminent? > Hi! > > This feature was added very r...

...ried various quoting without > success. > > > Didn't try escaping yet. > > > > > > > > > 2) Instead of string, return a key value table. you can have spaces in > > > values. > > > > > > > > > > > Does this work for auth_passdb_lookup too, or just auth_userdb_lookup? > I've > > been returning a table with auth_userdb_lookup just fine. But when I try > > using it with passdb (and despite being very very sure that a 'password' > > key exists in the table I'm returning from auth_passdb_lookup()...

.... > > > > > > > > > > > > > > > 2) Instead of string, return a key value table. you can have > spaces in > > > > > values. > > > > > > > > > > > > > > > > > > > Does this work for auth_passdb_lookup too, or just > auth_userdb_lookup? > > > I've > > > > been returning a table with auth_userdb_lookup just fine. But when I > try > > > > using it with passdb (and despite being very very sure that a > 'password' > > > > key exists in...

...ace to an underscore as a workaround, but I'm > curious if there's a better way. I tried various quoting without success. > Didn't try escaping yet. > > > 2) Instead of string, return a key value table. you can have spaces in > values. > > > Does this work for auth_passdb_lookup too, or just auth_userdb_lookup? I've been returning a table with auth_userdb_lookup just fine. But when I try using it with passdb (and despite being very very sure that a 'password' key exists in the table I'm returning from auth_passdb_lookup() -- I'm logging it one line abov...

...wesome: https://wiki2.dovecot.org/AuthDatabase/Lua Any words of wisdom on using it? I'd be putting a bunch of mysql logic in it. Any horrible gotchas there? When it says 'blocking', should I assume that means that a auth worker process will *not* accept any new auth lookups until both auth_passdb_lookup() and auth_userdb_lookup() have completed (in which I'd be doing several mysql calls)? If that's the case, I assume that the number of auth workers should be bumped up. And is a 2.3 release fairly imminent?

...vecot.org/AuthDatabase/Lua > > Any words of wisdom on using it? I'd be putting a bunch of mysql logic in > it. Any horrible gotchas there? When it says 'blocking', should I assume > that means that a auth worker process will *not* accept any new auth > lookups until both auth_passdb_lookup() and auth_userdb_lookup() have > completed (in which I'd be doing several mysql calls)? If that's the case, > I assume that the number of auth workers should be bumped up. > > And is a 2.3 release fairly imminent? Hi! This feature was added very recently, and there is very l...

...>>> Any words of wisdom on using it? I'd be putting a bunch of mysql logic in >>> it. Any horrible gotchas there? When it says 'blocking', should I assume >>> that means that a auth worker process will *not* accept any new auth >>> lookups until both auth_passdb_lookup() and auth_userdb_lookup() have >>> completed (in which I'd be doing several mysql calls)? If that's the >>> case, >>> I assume that the number of auth workers should be bumped up. >>> >>> And is a 2.3 release fairly imminent? >>> >&g...

Hi, I'm setting up a Postfic and Dovecot with LDAP email server. My users in LDAP is like this: dn: uid=firstname,ou=People,dc=domain,dc=com uid: firstname uidNumber: 4025 gidNumber: 4025 givenName: firstname objectClass: top objectClass: person objectClass: posixAccount objectClass: shadowAccount objectClass: organizationalPerson objectClass: