search for: auth_userdb_lookup

...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 above the return...

...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 &...

...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 ver...

...ound, 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 above the return), the passdb auth f...

...; 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...

...> > > > > > > > 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 aut...

...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?

...----------- >>> >>> I added it in 10-auth.conf behind the LDAP auth include statement. >>> >>> The Lua script looks like this: >>> -------------------------------------------------- >>> require('io') >>> >>> function auth_userdb_lookup(req) >>> local bindpwfile = "/etc/dovecot/ldap-auth-userdb.secret" >>> local base = "ou=people,ou=it,dc=roessner-net,dc=de" >>> local binddn = "cn=dovecot," .. base >>> >>> local cmd = [=[ >>> /bin/sh -c "ld...

...a blocking=yes > } > -------------------------------------------------- > > I added it in 10-auth.conf behind the LDAP auth include statement. > > The Lua script looks like this: > -------------------------------------------------- > require('io') > > function auth_userdb_lookup(req) > local bindpwfile = "/etc/dovecot/ldap-auth-userdb.secret" > local base = "ou=people,ou=it,dc=roessner-net,dc=de" > local binddn = "cn=dovecot," .. base > > local cmd = [=[ > /bin/sh -c "ldapsearch -LLL -ZZ -y $bindpwfile -xD $b...

...-------------- >>> >>> I added it in 10-auth.conf behind the LDAP auth include statement. >>> >>> The Lua script looks like this: >>> -------------------------------------------------- >>> require('io') >>> >>> function auth_userdb_lookup(req) >>> local bindpwfile = "/etc/dovecot/ldap-auth-userdb.secret" >>> local base = "ou=people,ou=it,dc=roessner-net,dc=de" >>> local binddn = "cn=dovecot," .. base >>> >>> local cmd = [=[ >>> /bin/sh -c &quo...

...a > > 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 little operational experie...

...args = file=/etc/dovecot/dovecot-auth-userdb.lua blocking=yes } -------------------------------------------------- I added it in 10-auth.conf behind the LDAP auth include statement. The Lua script looks like this: -------------------------------------------------- require('io') function auth_userdb_lookup(req) local bindpwfile = "/etc/dovecot/ldap-auth-userdb.secret" local base = "ou=people,ou=it,dc=roessner-net,dc=de" local binddn = "cn=dovecot," .. base local cmd = [=[ /bin/sh -c "ldapsearch -LLL -ZZ -y $bindpwfile -xD $binddn -b $base '(rnsMSDov...

...f 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! >> >>...

> On 28/08/2019 21:01 R.N.S. via dovecot <dovecot at dovecot.org> wrote: > > > > Am 28.08.2019 um 19:46 schrieb Jakobus Sch?rz via dovecot <dovecot at dovecot.org>: > > > > I think, i had the same problem as you. > > > > When dovecot runs lmtp, no user is logged in, so there is no user from > > which you can get groups. So i think, my

...------------------------------------------- >> >> I added it in 10-auth.conf behind the LDAP auth include statement. >> >> The Lua script looks like this: >> -------------------------------------------------- >> require('io') >> >> function auth_userdb_lookup(req) >> local bindpwfile = "/etc/dovecot/ldap-auth-userdb.secret" >> local base = "ou=people,ou=it,dc=roessner-net,dc=de" >> local binddn = "cn=dovecot," .. base >> >> local cmd = [=[ >> /bin/sh -c "ldapsearch -LLL -ZZ -...