File

mod_invites_register/README.markdown @ 4515:2e33eeafe962

mod_muc_markers: Prevent any markers from reaching the archive, even if untracked Original intention was to leave alone things that this module isn't handling. However markers in archives are just problematic without more advanced logic about what is markable and what is not. It also requires a more advanced query in mod_muc_rai to determine the latest markable message instead of the latest archived message. I'd rather keep the "is archivable" and "is markable" definition the same for simplicity. I don't want to introduce yet another set of rules for no reason. No markers in MAM.
author Matthew Wild <mwild1@gmail.com>
date Mon, 22 Mar 2021 15:55:02 +0000
parent 4224:816c2fa1ca84
child 4635:415264707251
line wrap: on
line source

---
labels:
- 'Stage-Beta'
summary: 'Allow account registration using invite tokens'
...

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

This module is part of the suite of modules that implement invite-based
account registration for Prosody. The other modules are:

- [mod_invites]
- [mod_invites_adhoc]
- [mod_invites_page]
- [mod_invites_register_web]
- [mod_invites_api]
- [mod_register_apps]

For details and a full overview, start with the [mod_invites] documentation.

Details
=======

This module allows clients to register an account using an invite ('preauth')
token generated by mod_invites. It implements the protocol described at
[docs.modernxmpp.org/client/invites](https://docs.modernxmpp.org/client/invites)
and [XEP-0401 version 0.3.0](https://xmpp.org/extensions/attic/xep-0401-0.3.0.html).

**Note to developers:** the XEP-0401 protocol is expected to change in the future,
though Prosody will attempt to maintain backwards compatibility with the 0.3.0 protocol
for as long as necessary.

This module is also responsible for implementing the optional server-side part
of [XEP-0379: Pre-Authenticated Roster Subscriptions](https://xmpp.org/extensions/xep-0379.html).

**Note to admins:** Loading this module will disable registration for users
without an invite token by default. Control this behaviour 

# Configuration

| Name                     | Description                                              | Default |
|--------------------------|----------------------------------------------------------|---------|
| registration_invite_only | Require an invitation token for all account registration | `true`  |

## Example: Invite-only registration

This setup enables registration **only** for users that have a valid
invite token.

``` {.lua}
allow_registration = true
registration_invite_only = true
```

## Example: Open registration

This setup allows completely **open registration**, even without
an invite token.

``` {.lua}
allow_registration = true
registration_invite_only = false
```