Fix account registration NATS SSL error
Table of Contents
Deferred from Sprint 18 on 2026-05-29 — not started; carried forward to product backlog. This page documents a story in Sprint 18. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
Goal
A user can register a new account from the login dialog's Register link
when the deployment permits self-registration. Today this fails: clicking
Create Account returns Account creation failed: NATS connect failed:
SSL Error, so registration cannot complete. The registration path's
NATS/TLS configuration needs investigating and fixing so account creation
succeeds (or fails with a clear, actionable message when registration is
disabled).
Status
| Field | Value |
|---|---|
| State | BACKLOG |
| Parent sprint | Sprint 18 |
| Now | Not yet started. |
| Waiting on | Nothing. |
| Next | Break the story into tasks. |
| Last touched | 2026-05-26 |
Acceptance
- The root cause of
NATS connect failed: SSL Erroron the registration path is identified (client TLS settings, NATS endpoint, or cert trust). - With self-registration enabled, submitting the Create Account form succeeds: the account is created and the user can then log in.
- When self-registration is disabled, the client reports that clearly rather than surfacing a raw NATS/SSL error.
- The user manual's registration note is updated to match the fixed behaviour.
Tasks
| Task | State | Start | End | Description |
Decisions
Out of scope
- The administrative toggle that enables/disables self-registration (assumed to exist server-side; only its client-facing behaviour is in scope here).