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.

--
-- A module to indicate if a MUC message qualifies as historic based on XEP-0334 hints
--

module:depends"muc_mam"

module:log("debug", "Module loaded");

module:hook("muc-message-is-historic", function (event)
  if (event.stanza:get_child("no-store", "urn:xmpp:hints") or
    event.stanza:get_child("no-permanent-store", "urn:xmpp:hints")) then
      module:log("debug", "Not archiving stanza: %s (urn:xmpp:hints)", event.stanza)
    return false
  elseif event.stanza:get_child("store", "urn:xmpp:hints") then
    return true
  else
    return nil
  end
end)