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.

include		/etc/openldap/schema/core.schema
# I needed the following two schema definitions for posixGroup; if you don't
# need it, don't include them
include         /etc/openldap/schema/cosine.schema
include         /etc/openldap/schema/nis.schema
# needed for inetOrgPerson so I can test jpegPhoto
include         /etc/openldap/schema/inetorgperson.schema

pidfile		/var/run/openldap/slapd.pid
argsfile	/var/run/openldap/slapd.args
database	bdb
suffix		"dc=example,dc=com"
rootdn		"cn=Manager,dc=example,dc=com"
rootpw		prosody
directory	/var/lib/openldap/openldap-data
index	objectClass	eq