Skip to content

Credential Lifecycle

  1. User fills form in AddCredentialModal.
  2. Secret fields are packaged by useEncryption().encryptCredential().
  3. Encrypted blob is written to credentials.secret_blob.
  4. Metadata is stored alongside encryption timestamp.
  1. EditCredentialModal loads row metadata and decrypts existing secret_blob if vault is unlocked.
  2. Updated secret values are re-encrypted.
  3. Update payload explicitly includes valid DB columns.
  1. Edit flow (EditCredentialModal) decrypts secret_blob when vault is unlocked and pre-fills form values.
  2. Detail flow (CredentialDetailModal) currently shows legacy plaintext columns and does not yet decrypt secret_blob.
  3. This means encrypted-only records are best inspected through edit flow at present.
  • CredentialDetailModal deletes row by id after user confirmation.
  • In-memory filtering by title, description, category, type, and tags.
  • Category list merged from default and user-specific categories.

Some legacy plaintext-oriented fields/components still exist; current expected secure path is secret_blob driven.