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.

#!/usr/bin/env python2

import sys

def auth(username, password):
	if username == "someone":
		return "1"
	return "0"

def respond(ret):
	sys.stdout.write(ret+"\n")
	sys.stdout.flush()

methods = {
	"auth": { "function": auth, "parameters": 2 }
}

while 1:
	line = sys.stdin.readline().rstrip("\n")
	method, sep, data = line.partition(":")
	if method in methods:
		method_info = methods[method]
		split_data = data.split(":", method_info["parameters"])
		if len(split_data) == method_info["parameters"]:
			respond(method_info["function"](*split_data))
		else:
			respond("error: incorrect number of parameters to method '%s'"%method)
	else:
		respond("error: method '%s' not implemented"%method)