view mod_block_outgoing/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 34fb3d239ac1
children
line wrap: on
line source

---
summary: 'Block outgoing stanzas from users'
...

Introduction
============

This module blocks all outgoing stanzas from a list of users.

Using
=====

Add mod_block_outgoing to the enabled modules in your config file:
``` {.lua}
modules_enabled = {
	-- ...
		"block_outgoing",
	-- ...
}
```

Either in a section for a certain host or the global section define which users and what stanzas to block:
``` {.lua}
block_outgoing_users = { "romeo@example.com", "juliet@example.com" }
block_outgoing_stanzas = { "message", "iq", "presence" }
```

block_outgoing_stanzas defaults to "message" if not specified.

Compatibility
=============

  ------- --------------
  trunk   Doesn't work (uses is_admin)
  0.12    Works
  0.11    Works
  ------- --------------