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-Stable'
summary: c2s connections throttling module
...

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

This module allows to throttle those client connections which exceed a
n\*seconds limit.

Usage
=====

Copy the module folder into your prosody modules directory. Place the
module between your enabled modules either into the global or a vhost
section.

Optional configuration directives:

``` {.lua}

cthrottler_logins_count = 3 -- number of login attempts allowed, default is 3
cthrottler_time = 60 -- .. in number of seconds, default is 60
```

Info
====

-   0.8, works
-   0.9, works