[ejabberd] ejabberd 17.04 external authentication: badarg

Marvin Gülker m-guelker at phoenixmail.de
Thu May 25 20:00:35 MSK 2017


On Wed, May 24, 2017 at 12:41:43PM +0200, Badlop wrote:
> Right, that's a good question. If I break the example perl script to
> not enter a loop and end immediately, ejabberd complains because it
> starts it and the script breaks constantly.

Yes, I see this too.

> I apply this patch: [...]
> Then at server start I see a line per vhost: [...]

I get this:

    2017-05-25 16:51:30.057 [info] <0.31.0> Application ejabberd started on node ejabberd at localhost
    2017-05-25 16:52:37.101 [debug] <0.328.0>@ejabberd_access_permissions:handle_call:139 Command 'check_account' execution allowed by rule 'console commands' (CallerInfo=#{caller_module => ejabberd_ctl})
    2017-05-25 16:52:37.101 [debug] <0.535.0>@ejabberd_commands:do_execute_command:633 Executing command ejabberd_auth:is_user_exists with Args=[<<"foo">>,<<"localhost">>]
    2017-05-25 16:52:37.102 [info] <0.535.0>@extauth:get_process_name:72 extauth process name: eauth_localhost0
    2017-05-25 16:52:37.102 [error] <0.535.0>@ejabberd_auth:is_user_exists:394 The authentication module ejabberd_auth_external returned an error
    when checking user <<"foo">> in server <<"localhost">>
    Error message: badarg

I applied the patch to 17.04 manually by editing the file as it didn't
apply cleanly using patch(1).

> In an erlang shell, I can also confirm the process is registered:
> > lists:member(eauth_localhost0, registered()).
> true

I get false here.


Blog: https://www.guelkerdev.de

More information about the ejabberd mailing list