mod_storage_ejabberdsql_readonly: Don't use MySQL-specific syntax util.sql should take care of transformation when MySQL is in use.

mod_client_management: Bail out retrieving tokens for user Fixes core/usermanager.lua:118: attempt to index a nil value (field '?')

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.

mod_http_oauth2: Restrict introspection to clients own tokens The introspection code was added before the client hash was added in 0860497152af which allows connecting tokens to clients.

mod_http_oauth2: Implement introspection endpoint "Tell me about this token"

mod_http_status: Add IP allowlisting capabilities Based on mod_http_openmetrics

mod_rest: Limit payload size (cf stanza size limits) Otherwise the limit would be defined by the HTTP stack.

mod_storage_s3: Add brief README

mod_storage_s3: Treat 404 to GET as a signal for empty data

mod_storage_s3: Use '@' as placeholder for empty (host) store slots Used when the server stores things for itself.