search for: auth_polici

> On 14 Dec 2017, at 8.30, Peter Mogensen <apm at one.com> wrote: > However... since the proxy use "nopassword", ALL passdb lookups result > in "success", so the proxy will never report an authentication failure > to the authpolicy server. Why not authenticate the sessions at the proxy level already? Is there any reason not to do that? Sami

Hi ... After the below thread, I wrote a patch to select on a node-by-node basis which auth-policy request should be done from that node. To my surprise the exact same functionality then turned up in 2.2.34 with just slightly different option names:* * *auth_policy_check_before_auth*: Whether to do policy lookup before authentication is started *auth_policy_check_after_auth*: Whether to do

On 09/15/2018 10:41 AM, Aki Tuomi wrote: > Point of sending the success ones is to maintain whitelist as well as > blacklist so you know which ones you should not tarpit anymore. We > know it does scale as we have very large deployments using the whole > three request per login model. > > "Success" in a proxy which is not it self authenticating is only whether it know

Hi, I was looking into the new Authentication Policy feature: https://wiki2.dovecot.org/Authentication/Policy I had kinda hoped that I would be able to enfore this in a proxy running in front of several backends. This proxy does not authenticate. It use "nopassword". But I realize that the "succes" reported in the final authpolicy req. (command=report) is not what is

i installed skype for asterisk i can send and recieve calls normaly how can i receive messages from another skype user i Succeed to send only using for example: exten => 2233,1,SkypeChatSend(fSkypeBcp,User,message text) how to receive messages using this code SKYPE_CHAT_RECEIVE(<account>,<from>,<timeout>),and where and how I should add this code in extensions.conf

On Wed, Sep 27, 2017 at 10:06 PM, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > > On 27.09.2017 20:14, Mark Moseley wrote: > > On Wed, Sep 27, 2017 at 10:03 AM, Marcus Rueckert <darix at opensu.se> > wrote: > > > >> On 2017-09-27 16:57:44 +0000, Mark Moseley wrote: > >>> I've been digging into the auth policy stuff with weakforced

On Wed, Sep 27, 2017 at 10:03 AM, Marcus Rueckert <darix at opensu.se> wrote: > On 2017-09-27 16:57:44 +0000, Mark Moseley wrote: > > I've been digging into the auth policy stuff with weakforced lately. > There > > are cases (IP ranges, so could be wrapped up in remote {} blocks) where > > it'd be nice to skip the auth policy (internal hosts that I can trust,

On Thu, Sep 28, 2017 at 9:34 AM, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > > On September 28, 2017 at 7:20 PM Mark Moseley <moseleymark at gmail.com> > wrote: > > > > > > On Wed, Sep 27, 2017 at 10:06 PM, Aki Tuomi <aki.tuomi at dovecot.fi> > wrote: > > > > > > > > > > > On 27.09.2017 20:14, Mark Moseley

On 27.09.2017 20:14, Mark Moseley wrote: > On Wed, Sep 27, 2017 at 10:03 AM, Marcus Rueckert <darix at opensu.se> wrote: > >> On 2017-09-27 16:57:44 +0000, Mark Moseley wrote: >>> I've been digging into the auth policy stuff with weakforced lately. >> There >>> are cases (IP ranges, so could be wrapped up in remote {} blocks) where >>>

I've set up google voice to chat with me: Forwards calls to: <me>@gmail.com and xmpp: [general] debug=no ; Enable debugging (disabled by default). autoprune=yes ; Auto remove users from buddy list. Depending on your ; setup (ie, using your personal Gtalk account for a test)

> On September 28, 2017 at 7:20 PM Mark Moseley <moseleymark at gmail.com> wrote: > > > On Wed, Sep 27, 2017 at 10:06 PM, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > > > > > > On 27.09.2017 20:14, Mark Moseley wrote: > > > On Wed, Sep 27, 2017 at 10:03 AM, Marcus Rueckert <darix at opensu.se> > > wrote: > > > >

When a caller calls my google voice phone number, I must answer, wait and press one to accept. Sometimes even that does not work. I have tried a few different things to get asterisk to place the call in an answered state and send the DTMF 1 with the Dial macro. I found Malcom Davenports wiki page regarding Google calling which has been very helpful in troubleshooting the issue.