ejabberd - Comments for "External auth program not being called"

I know this post is 6 years

scags9876 — Tue, 19 May 2015 15:17:55 +0000

I know this post is 6 years old, but I just ran into the same problem using an external auth perl script. It was apparently working to authenticate using an oauth2 endpoint, but was emitting no logs.

Fixed it by turning on autoflush for my file handle. see:
http://www.perlmonks.org/?node_id=280025

Checked... permissions are OK

paolo — Tue, 24 Feb 2009 16:56:50 +0000

Make sure you also check permissions of the authentication script itself, it must be executable. It wouldn't be strange to miss this, when you write for the web you don't need to take care of this, but in cli mode you do.

Further each time you edit the script or permissions, restart ejabberd or you won't get any change.

Checked... permissions are OK

ggalmazor — Tue, 10 Feb 2009 09:33:08 +0000

Hi, thanks for your reply!

I've double checked permissions for the log file and it's 666 (everyone can write and read). Also, if ejabberd didn't have permissions to write in the logfile, i should probably see something in it's log but there is no signs of nothing happening when i try to authenticate.

I think that the problem might be somewhere else. I forgot to mention that i'm using the standard ubuntu's repository ejabberd version. I'll try to download it from the trunk and see what happens...

write permissions to write log file

mfoss — Sun, 08 Feb 2009 22:01:05 +0000

ggalmazor wrote:

When i try to log in (web or IM client) i see lines in /var/log/ejabberd/ejabberd.log but none in /var/log/JabberAuth.log (the script's log file).

Maybe the problem is permissions to write log file? I tried that script with ejabberd trunk SVN and works.

To get it to log, I changed the line to

  public $logfile = '/tmp/JabberAuth.log';

When ejabberd starts, it starts the script for each different vhost you have. In my case I have two vhosts in ejabberd.cfg, so I see:

$ ps -C JabberAuth.class.php
  PID TTY          TIME CMD
 6122 ?        00:00:00 JabberAuth.clas
 6123 ?        00:00:00 JabberAuth.clas

When I try to login with a Jabber client, the script log file is created with some lines:

$ cat JabberAuth.log
2009-02-08 22:58:03 Reading 30 bytes ...
2009-02-08 22:58:03 IN: auth:badlop:localhost:pass123
2009-02-08 22:58:03 GO: auth:badlop:localhost:pass123
2009-02-08 22:58:03 data length is : 30