prosody-modules
d3ebaef1ea7a
misc/lnav/prosody.json

Find changesets by keywords by author, files, the commit message, revision number or hash, or revset expression.

Software / code / prosody-modules

File

misc/lnav/prosody.json @ 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
parent 4880:f64d13d9b76b
child 5496:3e6d1e248dc1
line wrap: on
line source

{
   "$schema" : "https://lnav.org/schemas/format-v1.schema.json",
   "prosody_log" : {
      "body-field" : "message",
      "description" : "The Prosody IM server log format",
      "level" : {
         "debug" : "^debug$",
         "error" : "^error$",
         "info" : "^info$",
         "warning" : "^warn$"
      },
      "level-field" : "loglevel",
      "multiline" : false,
      "ordered-by-time" : true,
      "regex" : {
         "standard" : {
            "pattern" : "^(?<timestamp>\\w{3} \\d{2} \\d{2}:\\d{2}:\\d{2})\\s+(?<loggername>\\S+)\\s+(?<loglevel>debug|info|warn|error)\\s+(?<message>.+)$"
         }
      },
      "sample" : [
         {
            "line" : "Jan 31 11:07:34 c2s565063fff480\tinfo\tClient connected"
         }
      ],
      "timestamp-field" : "timestamp",
      "timestamp-format" : "%b %d %H:%M:%S ",
      "title" : "Prosody log",
      "url" : "https://prosody.im/doc/logging",
      "value" : {
         "loggername" : {
            "identifier" : true,
            "kind" : "string"
         },
         "payload" : {
            "kind" : "xml"
         }
      }
   }
}