ejabberd - Comments for "ejabberd_auth_sasl-1.0.0"

I've uploaded the patch

mfoss — Tue, 30 Jan 2007 21:36:37 +0000

I've uploaded the patch (slightly fixed), and added a page to Contributions: Authenticate Against SASL.

SASL

axet — Tue, 30 Jan 2007 15:14:10 +0000

Hi!

* SASL is protocol specification for security authentication, is not authentication mechanism like PAM. I use SASL not by specification, because transport layer implementation available in ejabber code.

Example:
SASL client - (network - sasl lib) - SASL server

SASL server library send client request to server side, and your server-side realization can pass thought client request to auth mechanism, supported by sasl library;

http://en.wikipedia.org/wiki/Simple_Authentication_and_Security_Layer

Next. I say about partial implementation of SASL library, because i use only SASL AUTH API, all transport layer eabberd specific.

* Auth api is very simply to PAM, but no configuration available at now.

* required ejabberd-1.1.2 only;

this patch better then pam patch because have correct exist_user function.

Some silly questions

mfoss — Tue, 30 Jan 2007 11:04:38 +0000

Hi, I'd like to add your patch to the Contributions page, but since I don't know much about SASL and PAM, let me ask some (silly) questions:

Is SASL a different authentication method than PAM?
If they are different, how can an admin configure ejabberd to use SASL, once he installs and compiles your patch?
Does your SASL method require the PAM patch to be installed, or are they independent?