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-Beta'
summary: Automatically populate vcard based on account details
...

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

It is possible for the user to supply more than just a username and
password when creating an account using
[mod\_register](https://prosody.im/doc/modules/mod_register). This
module automatically copies over that data to the user's vcard.

Details
=======

There is no configuration for this module, just add it to
modules\_enabled as normal.

Note that running this on a public-facing server that prompts for email
during registration will make the user's email address publicly visible
in their vcard.

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

  ----- -------
  0.9   Works
  ----- -------