Mercurial > prosody-modules
view mod_invites_tracking/mod_invites_tracking.lua @ 5264:d3ebaef1ea7a
mod_http_oauth2: Correctly verify OAuth client credentials on revocation
Makes no sense to validate against username and password here, or using
a token to revoke another token, or itself?
In fact, upon further discussion, why do you need credentials to revoke
a token? If you are not supposed to have the token, revoking it seems
the most responsible thing to do with it, so it should be allowed, while
if you are supposed to have it, you should be allowed to revoke it.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Tue, 21 Mar 2023 21:57:18 +0100 |
parents | 32f1f18f4874 |
children |
line wrap: on
line source
local tracking_store = module:open_store("invites_tracking"); module:hook("user-registered", function(event) local validated_invite = event.validated_invite or (event.session and event.session.validated_invite); local new_username = event.username; local invite_id = nil; local invite_source = nil; if validated_invite then invite_source = validated_invite.additional_data and validated_invite.additional_data.source; invite_id = validated_invite.token; end tracking_store:set(new_username, {invite_id = validated_invite.token, invite_source = invite_source}); module:log("debug", "recorded that invite from %s was used to create %s", invite_source, new_username) end); -- " " is an invalid localpart -> we can safely use it for store metadata tracking_store:set(" ", {version="1"});