Skip to content

Auth: accounts, passkeys and API keys #2

Closed

Description

@ParallelEntrepreneur

The open Worker authenticates with StaticApiKeys (SHA-256 digests in config). The hosted service needs real accounts.

  • Sign-in with passkeys (harness auth-passkeys) and an email link fallback.
  • Issued API keys (gw_live_…), hashed at rest, listed and revoked from the dashboard.
  • An ApiKeys implementation over that store, supplied through Services (private crate, see the open-core issue).
  • Account deletion removes the account, keys and the My voice style summary.

Activity

  1. ParallelEntrepreneur commented on Oct 10, 2026

    @ParallelEntrepreneur
    ContributorAuthor

    Colonizer claim on #2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    colonizer:claimedA Colonizer colony on some mothership is working this issuecolonizer:host:archlinuxThe Colonizer mothership holding this issue's claim

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions