Mercurial > prosody-modules
annotate mod_log_sasl_mech/mod_log_sasl_mech.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 | 4baaa5a66a5a |
children | 5ff8022466ab |
rev | line source |
---|---|
1292
2d061333d0c2
mod_log_sasl_mech: Logs authentication mechanism used
Kim Alvefur <zash@zash.se>
parents:
diff
changeset
|
1 |
2d061333d0c2
mod_log_sasl_mech: Logs authentication mechanism used
Kim Alvefur <zash@zash.se>
parents:
diff
changeset
|
2 module:hook("authentication-success", function (event) |
1393
4baaa5a66a5a
mod_log_sasl_mech: Log SASL mechanism attached to session
Kim Alvefur <zash@zash.se>
parents:
1292
diff
changeset
|
3 local session = event.session; |
4baaa5a66a5a
mod_log_sasl_mech: Log SASL mechanism attached to session
Kim Alvefur <zash@zash.se>
parents:
1292
diff
changeset
|
4 local sasl_handler = session.sasl_handler; |
4baaa5a66a5a
mod_log_sasl_mech: Log SASL mechanism attached to session
Kim Alvefur <zash@zash.se>
parents:
1292
diff
changeset
|
5 session.log("info", "Authenticated with %s", sasl_handler and sasl_handler.selected or "legacy auth"); |
1292
2d061333d0c2
mod_log_sasl_mech: Logs authentication mechanism used
Kim Alvefur <zash@zash.se>
parents:
diff
changeset
|
6 end); |