view mod_lastlog2/README.markdown @ 5285:8e1f1eb00b58

mod_sasl2_fast: Fix harmless off-by-one error (invalidates existing tokens!) Problem: This was causing the key to become "<token>--cur" instead of the expected "<token>-cur". As the same key was used by the code to both set and get, it still worked. Rationale for change: Although it worked, it's unintended, inconsistent and messy. It increases the chances of future bugs due to the unexpected format. Side-effects of change: Existing '--cur' entries will not be checked after this change, and therefore existing FAST clients will fail to authenticate until they attempt password auth and obtain a new FAST token. Existing '--cur' entries in storage will not be cleaned up by this commit, but this is considered a minor issue, and okay for the relatively few FAST deployments.
author Matthew Wild <mwild1@gmail.com>
date Wed, 29 Mar 2023 16:12:15 +0100
parents fd582067c732
children c5df6d53f17f
line wrap: on
line source

---
labels:
- 'Stage-Beta'
summary: Record last timestamp of events
---

# Introduction

Similar to [mod_lastlog], this module records the last timestamp of
various events, but keeps the last timestamp per type of event, instead
of the last event.

# Usage

As with all modules, copy it to your plugins directory and then add it
to the modules\_enabled list:

``` {.lua}
modules_enabled = {
  -- other modules
  "lastlog2",
}
```

# Configuration

There are some options you can add to your config file:

  Name                   Type      Default   Description
  ---------------------- --------- --------- ---------------------------------
  lastlog\_ip\_address   boolean   false     Log the IP address of the user?

# Usage

You can check a user's last activity by running:

    prosodyctl mod_lastlog username@example.com

# Compatibility

  Version   State
  --------- -------
  Any       *TBD*