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-Auth'
summary: Wordpress authentication module
...

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

This module allows you to authenticate against an Wordpress database.

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

SQL connection paramaters are identical to those of [SQL
storage](https://prosody.im/doc/modules/mod_storage_sql).

    authentication = "wordpress"
    wordpress_table_prefix = "wp_" -- default table prefix
    sql = { -- See documentation for SQL storage
        driver = "MySQL";
        database = "my_wordpress";
        host = "localhost";
        username = "prosody";
        password = "secretpassword";
    }

Compatibility
=============

Prosody 0.8+