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.

---
labels:
- Stage-Beta
summary: "XEP-0198 integration with SASL2"
rockspec:
  dependencies:
  - mod_sasl2
---

Add support for inlining stream management negotiation into the SASL2 process.

**Note: At the time of writing (November 2022), this module implements a
version of XEP-0198 that is still working its way through the XSF standards
process. For more information and current status, see [PR #1215](https://github.com/xsf/xeps/pull/1215).**

This module depends on [mod_sasl2] and [mod_sasl2_bind2]. It exposes no
configuration options.