mod_storage_appendmap: Include timestamps when appending data Meant to give some sense of when each piece of data was added, to aid in debugging changes or manual rollbacks.

mod_storage_appendmap: Implement item/user iteration methods

mod_http_health: Copypaste IP access control code

mod_dnsupdate: Support advertising explicit non-existence of service

mod_http_admin_api: Support for adding/removing group MUCs

mod_groups_muc_bookmarks: Update bookmarks when a group MUC is added/removed

mod_groups_internal: Update to support multiple MUCs per group This was a feature request for Snikket.

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.