File

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.

---
labels:
- 'Stage-Alpha'
- 'Type-S2SAuth'
summary: Monkeysphere certificate checking for s2s
---

## Introduction

[Monkeysphere](http://web.monkeysphere.info/) is a project aiming to
introduce PGP's web of trust to protocols such as SSH and TLS (which
XMPP uses).

## Details

This module is currently just a prototype, it has numerous issues and is
**not** suitable for production use.

## Compatibility

  ------- -----------------------------
  trunk   Works (not tested recently)
  0.11    Works (not tested)
  0.10    Does not work
  0.9     Does not work
  ------- -----------------------------