Security: pairing device auth + per-platform authorization #752

Closed
opened 2026-10-27 13:37:36 +00:00 by sam · 0 comments
Owner

Remaining: implement portal magic-link login. Issue a single-use, time-bounded login link and deliver it over a messaging channel so the recipient can sign into the web portal without a password.

Acceptance: the token is single-use and rejected on replay; it expires; it is bound to one intended user; the link is delivered into that user chat through the configured channel (Telegram first); and an operator can request one from the web UI.

Groundwork to reuse, not rebuild: internal/pairing/ already mints and verifies codes - salted hashing, constant-time comparison, expiry, rate limiting - so it should be the token source rather than a second scheme invented beside it.

Open question this lane must settle: how the recipient is bound to the requesting portal user, given per-channel identity derivation is currently unresolved (see archie-core-c1qx).

Supersedes the earlier framing of this bead, which described Hermes-style pairing and device auth: the pairing backend already exists, so that is not the work. Reworded 2026-09-22; the original text is in Dolt history.

Notes

docs/prds/hermes-gap-analysis.md (referenced above) was intentionally deleted in commit 65aa5b4 ('chore: cleanup', 2026-07-28) after it had already spawned this and ~14 sibling beads issues from its 60 identified gaps — it is not a broken link to restore. This issue's description is the surviving record of its slice of that analysis.
Maintainer 2026-09-22: REDIRECT. The pairing/auth content as written is not the wanted feature. Pairing infrastructure already exists (internal/pairing/), and its allowlist counterpart is the code c1qx proved unreachable in production. What is wanted instead: exposing magic links through the web UI. Next: rewrite the description around magic-link exposure; verify the pairing backend is complete as a precondition.
Maintainer redirect 2026-09-22: the wanted feature is sharing a magic link over a messaging channel for one-time portal login - not Hermes-parity device pairing. Pairing infrastructure already exists in internal/pairing/ (code_test.go), and its allowlist counterpart is the code archie-core-c1qx proved unreachable in production.

Close reason

Closed


Imported from beads archie-core-1786637495743-227-dad8a377 · GitHub #248 · type feature · priority P2 · created 2026-08-08 · closed 2026-10-01

Remaining: implement portal magic-link login. Issue a single-use, time-bounded login link and deliver it over a messaging channel so the recipient can sign into the web portal without a password. Acceptance: the token is single-use and rejected on replay; it expires; it is bound to one intended user; the link is delivered into that user chat through the configured channel (Telegram first); and an operator can request one from the web UI. Groundwork to reuse, not rebuild: internal/pairing/ already mints and verifies codes - salted hashing, constant-time comparison, expiry, rate limiting - so it should be the token source rather than a second scheme invented beside it. Open question this lane must settle: how the recipient is bound to the requesting portal user, given per-channel identity derivation is currently unresolved (see archie-core-c1qx). Supersedes the earlier framing of this bead, which described Hermes-style pairing and device auth: the pairing backend already exists, so that is not the work. Reworded 2026-09-22; the original text is in Dolt history. ### Notes docs/prds/hermes-gap-analysis.md (referenced above) was intentionally deleted in commit 65aa5b4 ('chore: cleanup', 2026-07-28) after it had already spawned this and ~14 sibling beads issues from its 60 identified gaps — it is not a broken link to restore. This issue's description is the surviving record of its slice of that analysis. Maintainer 2026-09-22: REDIRECT. The pairing/auth content as written is not the wanted feature. Pairing infrastructure already exists (internal/pairing/), and its allowlist counterpart is the code c1qx proved unreachable in production. What is wanted instead: exposing magic links through the web UI. Next: rewrite the description around magic-link exposure; verify the pairing backend is complete as a precondition. Maintainer redirect 2026-09-22: the wanted feature is sharing a magic link over a messaging channel for one-time portal login - not Hermes-parity device pairing. Pairing infrastructure already exists in internal/pairing/ (code_test.go), and its allowlist counterpart is the code archie-core-c1qx proved unreachable in production. ### Close reason Closed --- _Imported from beads `archie-core-1786637495743-227-dad8a377` · GitHub #248 · type feature · priority P2 · created 2026-08-08 · closed 2026-10-01_
sam added the mediumfeature labels 2026-10-27 13:37:36 +00:00
sam self-assigned this 2026-10-27 13:37:36 +00:00
sam closed this issue 2026-10-27 13:37:36 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#752