File

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.

# Introduction

This module implements [XEP-xxxx: Room Activity Indicators](https://xmpp.org/extensions/inbox/room-activity-indicators.html).

## Requirements

This module currently depends on mod_muc_markers, so review the requirements for that module.

# Configuring

## Enabling

``` {.lua}
Component "rooms.example.net" "muc"
modules_enabled = {
    "muc_rai";
    "muc_markers";
    "muc_mam";
}
```

## Settings

|Name |Description |Default |
|-----|------------|--------|
|muc_rai_max_subscribers| Maximum number of active subscriptions allowed | 1024 |

# Compatibility

Requires Prosody trunk (2020-04-15+).