Software /
code /
prosody-modules
File
mod_http_auth_check/README.markdown @ 5390:f2363e6d9a64
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!
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Sun, 30 Apr 2023 16:13:40 +0200 |
parent | 3448:c4db126a9f04 |
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