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.

---
labels:
- 'Stage-Alpha'
summary: Require visitors to accept something before being allowed in a room
...

# Introduction

This module sends a message to visitors of a room, prompting them to accept or reject it.

They get kicked if they reject it, and become members if they accept it.

# Setup

```lua
Component "rooms.example.org" "muc"
	modules_enabled = {
		"muc_require_tos";
	}
	tos_welcome_message = "Please read and accept the TOS of this service: https://lurk.org/TOS.txt"
	tos_yes_message = "Thanks, and welcome here!"
	tos_no_message = "Too bad."
```

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

  ----- -----
  trunk Works
  ----- -----