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:
- 'Type-Auth'
summary: Another take on LDAP authentication
...

Introduction
============

See [mod\_lib\_ldap](mod_lib_ldap.html) for more information.

Installation
============

You must install [mod\_lib\_ldap](mod_lib_ldap.html) to use this module.
After that, you need only copy mod\_auth\_ldap2.lua to your Prosody
installation's plugins directory.

Configuration
=============

In addition to the configuration that [mod\_lib\_ldap](mod_lib_ldap.html)
itself requires, this plugin also requires the following fields in the
ldap section:

-   user.filter
-   admin (optional)

See the README.html distributed with [mod\_lib\_ldap](mod_lib_ldap.html) for
details.