prosody-modules
527c747711f3
mod_muc_log_http/README.markdown
Software / code / prosody-modules
File
mod_muc_log_http/README.markdown @ 5705:527c747711f3
mod_http_oauth2: Limit revocation to clients own tokens in strict mode
RFC 7009 section 2.1 states:
> The authorization server first validates the client credentials (in
> case of a confidential client) and then verifies whether the token was
> issued to the client making the revocation request. If this
> validation fails, the request is refused and the client is informed of
> the error by the authorization server as described below.
The first part was already covered (in strict mode). This adds the later
part using the hash of client_id recorded in 0860497152af
It still seems weird to me that revoking a leaked token should not be
allowed whoever might have discovered it, as that seems the responsible
thing to do.
| author | Kim Alvefur <zash@zash.se> |
|---|---|
| date | Sun, 29 Oct 2023 11:30:49 +0100 |
| parent | 1821:79b9bd84b91c |
line wrap: on
line source
--- labels: - 'Stage-Beta' summary: Provides a web interface to stored chatroom logs ... Introduction ============ This module provides a built-in web interface to view chatroom logs stored by [mod\_muc\_log](mod_muc_log.html). Installation ============ Just copy the folder muc\_log\_http as it is, into the modules folder of your Prosody installation. Configuration Details ===================== Example configuration: Component "conference.example.com" "muc" modules_enabled = { ..... "muc_log"; "muc_log_http"; ..... } muc_log_http = { -- These are the defaults show_join = true; show_presences = true; show_status = true; theme = "prosody"; url_base = "muc_log"; } **show\_join** sets the default for showing joins or leaves. **show\_status** sets the default for showing status changes. The web interface would then be reachable at the address: http://conference.example.com:5280/muc_log/ TODO ==== - Log bans correctly - Quota \~ per day ?! - Testing testing :)
