mod_http_xep227: Add support for import via APIs rather than direct store manipulation
In particular this transitions PEP nodes and data to be imported via mod_pep's
APIs, fixing issues with importing at runtime while PEP data may already be
live in RAM.
Next obvious candidate for this approach is rosters, so clients get immediate
roster pushes and other special handling (such as emitting subscribes to reach
the desired subscription state).
---
labels:
- 'Stage-Deprecated'
- 'Type-Auth'
summary: 'Authentication via external script/process (DEPRECATED)'
...
Introduction
============
Allow client authentication to be handled by an external script/process.
:::{.alert .alert-warning}
**Warning:** This module is not currently maintained, and may be buggy and insecure in
certain configurations/environments. It is **not** recommended for production use. Please
use one of the [many other authentication modules](/type_auth).
:::
Installation
============
mod\_auth\_external\_insecure depends on a Lua module called
[lpty](http://www.tset.de/lpty/). You can install it on many platforms
using [LuaRocks](http://luarocks.org/), for example:
sudo luarocks install lpty
Configuration
=============
As with all auth modules, there is no need to add this to
modules\_enabled. Simply add in the global section, or for the relevant
hosts:
authentication = "external_insecure"
These options are specific to mod\_auth\_external\_insecure:
-------------------------- -------------------------------------------------------------------------------------------------------------------------
external\_auth\_protocol May be "generic" or "ejabberd" (the latter for compatibility with ejabberd external auth scripts. Default is "generic".
external\_auth\_command The command/script to execute.
-------------------------- -------------------------------------------------------------------------------------------------------------------------
Two other options are also available, depending on whether the module is
running in 'blocking' or 'non-blocking' mode:
--------------------------- -------------- ------------------------------------------------------------------------------------------------------------------
external\_auth\_timeout blocking The number of seconds to wait for a response from the auth process. Default is 5.
external\_auth\_processes non-blocking The number of concurrent processes to spawn. Default is 1, increase to handle high connection rates efficiently.
--------------------------- -------------- ------------------------------------------------------------------------------------------------------------------
Blocking vs non-blocking
------------------------
Non-blocking mode is experimental and is disabled by default.
Enable at your own risk if you fulfil these conditions:
- Running Prosody trunk ([nightly](http://prosody.im/nightly/) build
414+) or Prosody 0.11.x.
- [libevent](http://prosody.im/doc/libevent) is enabled in the config,
and LuaEvent is available.
- lpty (see installation above) is version 1.0.1 or later.
```lua
external_auth_blocking = false;
```
Protocol
========
Prosody executes the given command/script, and sends it queries.
Your auth script should simply read a line from standard input, and
write the result to standard output. It must do this in a loop, until
there's nothing left to read. Prosody can keep sending more lines to the
script, with a command on each line.
Each command is one line, and the response is expected to be a single
line containing "0" for failure or "1" for success. Your script must
respond with "0" for anything it doesn't understand.
There are three commands used at the moment:
auth
----
Check if a user's password is valid.
Example: `auth:username:example.com:abc123`
Note: The password can contain colons. Make sure to handle that.
isuser
------
Check if a user exists.
Example: `isuser:username:example.com`
setpass
-------
Set a new password for the user. Implementing this is optional.
Example: `setpass:username:example.com:abc123`
Note: The password can contain colons. Make sure to handle that.
ejabberd compatibility
---------------------
ejabberd implements a similar protocol. The main difference is that
Prosody's protocol is line-based, while ejabberd's is length-prefixed.
Add this to your config if you need to use an ejabberd auth script:
external_auth_protocol = "ejabberd"
Compatibility
=============
----- -------
0.8 Works
0.9 Works
----- -------