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.

Developer Utilities/Tests
=========================

This directory exists for reasons of sanity checking.  If you wish
to run the tests, set up Prosody as you normally would, and install the LDAP
modules as normal as well.  Set up OpenLDAP using the configuration directory
found in this directory (slapd.conf), and run the following command to import
the test definitions into the LDAP server:

    ldapadd -x -w prosody -D 'cn=Manager,dc=example,dc=com' -f posix-users.ldif

Then just run prove (you will need perl and AnyEvent::XMPP installed):

    prove t