view mod_lastlog/README.markdown @ 5682:527c747711f3

mod_http_oauth2: Limit revocation to clients own tokens in strict mode RFC 7009 section 2.1 states: > The authorization server first validates the client credentials (in > case of a confidential client) and then verifies whether the token was > issued to the client making the revocation request. If this > validation fails, the request is refused and the client is informed of > the error by the authorization server as described below. The first part was already covered (in strict mode). This adds the later part using the hash of client_id recorded in 0860497152af It still seems weird to me that revoking a leaked token should not be allowed whoever might have discovered it, as that seems the responsible thing to do.
author Kim Alvefur <zash@zash.se>
date Sun, 29 Oct 2023 11:30:49 +0100
parents dd6313ddd3e0
children
line wrap: on
line source

---
labels:
- 'Stage-Beta'
summary: Log last login time
...

Introduction
============

Simple module that stores the timestamp of when a user logs in.

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
  "lastlog",
}
```

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?
  lastlog\_stamp\_offline   boolean false   Add timestamp to offline presence?

Usage
=====

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

    prosodyctl mod_lastlog username@example.com

Compatibility
=============

  ----- -------
  0.9   Works
  ----- -------