Mercurial > prosody-modules
view mod_storage_memory/README.md @ 6319:04c3273cb81f
mod_auth_cyrus: Add empty 'profile' table to SASL handler objects
This is for compatibility with Prosody's built-in util.sasl objects.
A SASL profile table usually includes methods supported by the backend, which
can be used by SASL mechanism handlers to perform operations (such as testing
the password). It also optionally contains a 'cb' field with channel binding
method handlers.
The Cyrus backend doesn't support channel binding, and doesn't have the same
concept of auth backend methods (it handles all that internally, and Prosody
has no insight or control over it).
Thus, we create an empty profile which informs Prosody that the SASL handler
does not support any of the auth or channel binding methods. Some features
will not work, but they didn't work anyway. This just makes it explicit.
This fixes a traceback in mod_sasl2_fast, which expected SASL handlers to
always contain a 'profile' field.
| author | Matthew Wild <mwild1@gmail.com> |
|---|---|
| date | Thu, 04 Sep 2025 10:14:46 +0100 |
| parents | ad3c709a1b16 |
| children |
line wrap: on
line source
--- labels: - 'Stage-Merged' - 'Type-Storage' - ArchiveStorage summary: 'Simple memory-only storage module' ... ::: {.alert .alert-warning} This module has been merged into [prosodys storage backend as "memory"][doc:storage] and is therefore obsolete. You will be redirected shortly. ::: Introduction ============ This module acts as a normal storage module for Prosody, but saves all data in memory only. All data is lost when the server stops. This makes it useful for testing, or certain specialized applications. Details ======= Because the accounts store will always begin empty, it is mostly useful combined with an authentication plugin which doesn't use Prosody's storage API, or with [mod\_auth\_any](mod_auth_any.html), or you can create user accounts manually each time the server starts. Compatibility ============= ----- ------- 0.9 Works ----- -------
