Mercurial > prosody-modules
view mod_storage_memory/README.markdown @ 5264:d3ebaef1ea7a
mod_http_oauth2: Correctly verify OAuth client credentials on revocation
Makes no sense to validate against username and password here, or using
a token to revoke another token, or itself?
In fact, upon further discussion, why do you need credentials to revoke
a token? If you are not supposed to have the token, revoking it seems
the most responsible thing to do with it, so it should be allowed, while
if you are supposed to have it, you should be allowed to revoke it.
| author | Kim Alvefur <zash@zash.se> |
|---|---|
| date | Tue, 21 Mar 2023 21:57:18 +0100 |
| parents | f5d4e23fa8f7 |
| children |
line wrap: on
line source
--- labels: - 'Stage-Merged' - 'Type-Storage' - ArchiveStorage summary: 'Simple memory-only storage module' ... 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 ----- -------