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.

Hola:

Si has recibido este email es porque has solicitado el reseteo de la
clave  de tu cuenta Jabber/XMPP {jid}

Para proceder con el cambio de clave, haz click en el siguiente enlace:

{url}

Si no has solicitado resetear tu clave, ignora este mensaje.

Atentamente, el equipo de mijabber.es