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.

---
description: File management for uploaded files
labels: 'Stage-Alpha'
---

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

This module exposes ad-hoc commands [XEP-0050] for listing uploaded files, and
later for managing them.

Configuration
=============

This module depends on mod\_http\_upload, and exposes ad-hoc commands for each
operation a user might do on their uploaded files.

The module can be added to the `modules_enabled` field on a host on which
mod\_http\_upload is loaded.

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

Works with Prosody trunk at least.