prosody-modules
527c747711f3
mod_migrate_http_upload/README.markdown
Software / code / prosody-modules
File
mod_migrate_http_upload/README.markdown @ 5705: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 |
| parent | 4469:6844733ad2f5 |
line wrap: on
line source
--- summary: mod_http_upload to mod_http_file_share migrator labels: - Stage-Alpha --- This is a migration script for converting records of [mod_http_upload] into the format used by the new [mod_http_file_share][doc:modules:mod_http_file_share] which will be available with Prosody 0.12 (currently in trunk). # Usage If your main `VirtualHost` is called "example.com" and your HTTP upload `Component` is called "upload.example.com", then this command would convert records of existing uploads via [mod_http_upload] to [mod_http_file_share][doc:modules:mod_http_file_share]: ```bash sudo prosodyctl mod_migrate_http_upload upload.example.com example.com ``` In order to preserve URLs you will need to configure the [path][doc:http#path_configuration] to be the same as mod_http_upload: ```lua Component "upload.example.com" "http_file_share" http_paths = { file_share = "/upload" } ```
