Skip to content

auth/authz or recommended way #54

Description

@westurner

Add support for authentication and authorization (auth/authz) to textual-web,
or an example/ of sufficient security to the docs,
or a warning that you should not host terminals over HTTP (with no login).

  • standard security policy

    • MUST NOT run a terminal over HTTP without auth.
      • Justification: Why were SSH and TLS/HTTPS created when we already had telnet and HTTP 1.0?
  • warning for the CLI user

    • textual-web is running without HTTPS.
      Autogenerating a --cert and assuming you meant --https
      Pass --http to allow running without HTTPS.

Presumably there's already a good enough way to add auth/authz to aiohttp apps?

Tasks

  • Add HTTPS support and args for certs
  • Autogenerate self-signed certs if none is specified?
  • Warn if not launched w/ HTTPS and a cert
  • Warn if not launched w/ auth
  • Add auth: {basic, digest, or token-based,} authentication and authorization;
    {user:u,
     permissions: {id: "/route/1", permissons: [read,write,],
     tokens: [{id: "token1", permissions: [read], dateCreated:, validUntil:}],
     session_keys: [{id: "abcd1", dateCreated:, validUntil: ],
     }
  • research auth/authz for aiohttp apps w/ and w/o a framework:

ASGI

aiohttp-asgi

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions