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 adds newly registered users as members to a specified MUC
room and sends them an invite. In a way, this is similar in purpose to
[mod_support_contact] and [mod_default_bookmarks].

# Example

    VirtualHost"example.com"
        modules_enabled = { "support_room" }
        support_room = "room@muc.example.com"
        support_room_inviter = "support@example.com"
        support_room_reason = "Invite new users to the support room"

    Component "muc.example.com"

# Compatibility

This module

  Version   Works
  --------- -------
  0.11.x    Yes
  0.10.x    No