DB, then redeploy. BAC creates its schema automatically.Create the first administrator. After initialization, issue that administrator a .bac credential file before signing out.
Your encrypted credential file is the possession factor. Its private key is decrypted locally and used only to sign a one-time challenge.
The .bac file and its password are never uploaded. BAC sends only the credential ID and cryptographic signature needed for authentication.
Each issued .bac file contains identity metadata plus an AES-256-GCM encrypted ECDSA P-256 private key. D1 stores the public key and lifecycle state. Copying the file alone is insufficient without its file password, and the server can revoke the credential at any time.
| Person | Username | Role | Status | Actions |
|---|
| Credential | Owner | Type | Status | Expires | Action |
|---|
| Time | Action | Target |
|---|
Export BAC server records as a JSON backup. Private keys are never included because they exist only inside user-owned .bac files.
Keep database backups and credential-file backups separately. Restoring D1 records cannot recreate a lost .bac private key.