8000 Authentication and authorization: login, roles and per-feature permissions · Issue #218 · simon-inkie/inkie-deck · GitHub
[go: up one dir, main page]

Skip to content

Authentication and authorization: login, roles and per-feature permissions #218

Open

Description

@simon-inkie

Deck has no login. Anyone who can reach the page can message agents (which are typed into live agents that can run commands) and, with Nudges on by default, create scheduled jobs. Today the protection is binding to loopback, which the setup script enforces.

Goal

Real authentication and authorization so Deck can be exposed beyond loopback safely: a shared server, a tunnel, a team, a phone.

To design

  • Login (local accounts first; passkeys or OIDC later) and sessions
  • Roles and per-feature permissions: read-only, chat, Nudges admin, settings, file access
  • Per-user audit trail of who sent what to which agent
  • Remote and mobile use

Interim

The loopback guard for Nudges and a boot warning for non-loopback HOST ship first, under #212.

Needs a SPEC under .specs/ before any build.

Activity

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

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      0