Mercurial > prosody-modules
view mod_http_auth_check/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 | c4db126a9f04 |
children |
line wrap: on
line source
--- labels: summary: 'Test account credentials using HTTP' ... Introduction ------------ This module lets you test whether a set of credentials are valid, using Prosody's configured authentication mechanism. This is useful as an easy way to allow other (e.g. non-XMPP) applications to authenticate users using their XMPP credentials. Syntax ------ To test credentials, issue a simple GET request with HTTP basic auth: GET /auth_check HTTP/1.1 Authorization: Basic <base64(jid:password)> Prosody will return a 2xx code on success (user exists and credentials are correct), or 401 if the credentials are invalid. Any other code may be returned if there is a problem handling the request. ### Example usage Here follows some example usage using `curl`. curl http://prosody.local:5280/auth_check -u user@example.com:secr1t