Mercurial > prosody-modules
view mod_throttle_unsolicited/README.markdown @ 5682: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 |
parents | 476afcbfb3e9 |
children |
line wrap: on
line source
--- rockspec: dependencies: - mod_track_muc_joins summary: Limit rate of outgoing unsolicited messages --- Introduction ============ This module limits the rate of outgoing unsolicited messages from local clients. Optionally, unsolicited messages coming in from remote servers may be limited per s2s conneciton. A message counts as "unsolicited" if the receiving user hasn't added the sending user to their roster. The module depends on [mod\_track\_muc\_joins] in order to allow sent messages to joined MUC rooms. Configuration ============= To set a limit on messages from local sessions: ``` {.lua} unsolicited_messages_per_minute = 10 ``` To enable limits on unsolicited messages from s2s connections: ``` {.lua} unsolicited_s2s_messages_per_minute = 100 ```