Mercurial > prosody-modules
view mod_s2s_auth_samecert/mod_s2s_auth_samecert.lua @ 5366:db4c66a1d24b
mod_http_oauth2: Fill in some client metadata defaults
Explicit > Implicit
Maybe we should actually use these for something as well? :)
It's is somewhat an open question of how strictly we should enforce
things in the client metadata given that it is somewhat extensible.
Especially some of these enum fields which have corresponding IANA
registries.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Tue, 25 Apr 2023 18:09:08 +0200 |
parents | c9397cd5cfe6 |
children |
line wrap: on
line source
module:set_global() local hosts = prosody.hosts; module:hook("s2s-check-certificate", function(event) local session, cert = event.session, event.cert; if not cert or session.direction ~= "incoming" then return end local outgoing = hosts[session.to_host].s2sout[session.from_host]; if outgoing and outgoing.type == "s2sout" and outgoing.secure and outgoing.conn:socket():getpeercertificate():pem() == cert:pem() then session.log("debug", "Certificate matches that of s2sout%s", tostring(outgoing):match("[a-f0-9]+$")); session.cert_identity_status = outgoing.cert_identity_status; session.cert_chain_status = outgoing.cert_chain_status; return true; end end, 1000);