mod_http_oauth2: Advertise the currently supported id_token signing algorithm This field is REQUIRED. The algorithm RS256 MUST be included, but isn't because we don't implement it, as that would require implementing a pile of additional cryptography and JWT stuff. Instead the id_token is signed using the client secret, which allows verification by the client, since it's a shared secret per OpenID Connect Core 1.0 § 10.1 under Symmetric Signatures. OpenID Connect Discovery 1.0 has a lot of REQUIRED and MUST clauses that are not supported here, but that's okay because this is served from the RFC 8414 OAuth 2.0 Authorization Server Metadata .well-known endpoint!

---
summary: Allow specified JIDs to bypass rate limits
...

This module allows you to configure a list of JIDs that should be allowed to
bypass rate limit restrictions.

It is designed for Prosody 0.11.x. Prosody 0.12.x supports this feature
natively.

## Configuration

First, enable this module by adding `"limits_exception"` to your
`modules_enabled` list.

Next, configure a list of JIDs to exclude from rate limiting:

```
unlimited_jids = { "user1@example.com", "user2@example.net" }
```

## Compatibility

Made for Prosody 0.11.x only.

Using this module with Prosody trunk/0.12 may cause unexpected behaviour.