Mercurial > prosody-modules

view mod_auth_ccert/README.markdown @ 5682:527c747711f3

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
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 0e3f5f70a51d
children
line wrap: on
line source

---
labels:
- 'Stage-Alpha'
- 'Type-Auth'
summary: Client Certificate authentication module
...

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

This module implements PKI-style client certificate authentication. You
will therefore need your own Certificate Authority. How to set that up
is beyond the current scope of this document.

Configuration
=============


    authentication = "ccert"
    certificate_match = "xmppaddr" -- or "email"

    c2s_ssl = {
        cafile = "/path/to/your/ca.pem";
        capath = false; -- Disable capath inherited from built-in default
        verify = {"peer"; "client_once"}; -- Ask for client certificate
        verifyext = {
            -- Don't validate client certs as if they were server certs
            lsec_ignore_purpose = false
        }
    }


Compatibility
=============

  ----------------- --------------
  trunk             Works
  0.10 and later    Works
  0.9 and earlier   Doesn't work
  ----------------- --------------