ejabberd-htpasswd
Yet another ejabberd authentication bridge that uses apache-style .htpasswd files.
Project
Installation
$ sudo apt-get install libffi-dev
$ pip install ejabberd-htpasswd
Configuration
Update the authentication configuration in your /etc/ejabberd/ejabberd.cfg file:
{auth_method, external}.
{extauth_program, "/usr/local/bin/ejabberd-htpasswd /path/to/htpasswd"}.
%% optional -- update as appropriate
%% {extauth_instances, 2}.
%% {extauth_cache, 300}.
Options
The ejabberd-htpasswd script takes one optional positional argument, the fully-qualified path to the “.htpasswd” file, and several optional parameters:
-d, --debug:
Enable debug mode for more stuff in the log files.
-l {FILENAME}, --log-file {FILENAME}:
The log file name, which will be rotated as defined by -s and -c; default: /var/log/ejabberd/auth-htpasswd.log.
-s BYTES, --log-size BYTES:
specify the maximum size of the log file in bytes before the log file is rotated; default: 1048576 (1 MB).
-c NUMBER, --log-count NUMBER:
specify the maximum number of log rotation files; default: 10.
-t EXPR, --domain-transform EXPR:
specify a “sed”-style substitution expression for domain name transformation; example: /.*\.example\.com$/example\.com/. Note that when placed in the ejabberd config file, several layers of escaping must be done, so you’ll need something like this to accomplish the above:
{extauth_program, "/usr/local/bin/ejabberd-htpasswd \\ -t /.*\\\\.example\\\\.com$/example.com/ \\ /path/to/htpasswd"}.
Metadata
Release files for ejabberd_htpasswd 0.1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| ejabberd_htpasswd-0.1.3.tar.gz | 17.4 kB | Without provenance | Details |
Release files / ejabberd_htpasswd-0.1.3.tar.gz
| Download URL | ejabberd_htpasswd-0.1.3.tar.gz |
|---|---|
| Size | 17.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4ae834bf6ae33cef1053b7481c3a95d210fcdc7e456019e72297f581239a477b
|
|
BLAKE2b-256 checksum How to use checksums |
9c78798542f931c089f6e84b8bf38fcd52a324a045f5a2b364ab62c962acbf4b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for ejabberd_htpasswd 0.1.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.