authentication: done(false) about node-ejabberd-auth HOT 4 CLOSED

Moin,

sorry for the late response, I've been quite busy here.
Passing false to the callback function should work perfectly, since the response to ejabberd is derived from checking your return value against true:

var data = result === true ? 0x1 : 0x0;

So passing anything else than true should yield to return 0x0 (aka "false") to the ejabberd server.
My own project uses true and false just fine, without the process terminating itself.

What does your log say when a failed auth terminates the process? Maybe this could help us find a clue to this unexpected behaviour.

from node-ejabberd-auth.

Hey mate,

we managed to trace the problem it back to the winston logging module. Removing the logging being done seemed to fix things up.

Many thanks

from node-ejabberd-auth.

Hi,

I think your problem here was that you did not configure a log file to use for winston (not to blame you - it's not documented by now), so winston crashed your node process. The update I just pushed should address this problem by disabling file logging altogether when no log configuration is given.

from node-ejabberd-auth.

Nice one, thank you mate :)

from node-ejabberd-auth.