Mercurial > prosody-modules
view mod_jsxc/README.markdown @ 5682:527c747711f3
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.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Sun, 29 Oct 2023 11:30:49 +0100 |
parents | 272a8e54f0c8 |
children |
line wrap: on
line source
--- rockspec: build: copy_directories: - templates dependencies: - mod_http_libjs summary: JSXC demo --- Try out JSXC easily by serving it from Prosodys built-in HTTP server. Uses [mod_http_libjs] to serve jQuery, on Debian you can `apt install libjs-jquery`. # Configuration mod_jsxc can be set up to either use resources from a separate HTTP server or serve resources from Prosody's built-in HTTP server. ## Using CDN `jsxc_cdn` : String. Base URL where JSXC resources are served from. Defaults to empty string. `jsxc_version` : String. Concatenated with the CDN URL. Defaults to empty string. ## Local resources Download a JSXC release archive and unpack it somewhere on your server. `jsxc_resources` : String. Path to the `dist` directory containing JSXC resources on the local file system. Disabled by default. ## Other options `jquery_url` : String. URL or relative path to jQuery. Defaults to `"/share/jquery/jquery.min.js"` which will work with [mod_http_libjs].