We should describe what it needs to be done to implement Parsec Auth and its impact on Parsec Server and libparsec:

• Parsec Auth API

  • Account creation (email+password)
  • Password update
  • User authentication + 2FA support
  • Get device registration key (allows to create device securisation key, the "classic" Parsec device key)
  • Store device registration key after identity validation (i.e. after invite)
  • List organizations for current authenticated user
  • List invitations for current authenticated user
  • Account recovery (TBD)
    • List Shamir configurations for current authenticated user
    • List devices already registered (per organization)
  • For the (not too distant) future
    • SSO support
    • Passkey/WebAuthn support
    • PKI support

• Parsec Server API (all token-protected routes)

  • List organizations of a user
  • List invitations of a user. Note these are received (not sent) invitations
  • List shamir of a user

• Libparsec

  • Support new APIs from Parsec Auth/Server
  • Generation of device registration key to be stored in Parsec Auth
  • Password derivation (from device registration key?)
  • Disable mountpoint
  • Decrypt documents on RAM (for visualization of supported file-types)
  • Download a document (for non-supported file types)
  • Device storage

Multi-tab browser support (for a different RFC?)