vault: remove temp connect/token diagnostic log

The crypto-shape question is answered (classic + v2 fields both present); drop
the diagnostic that logged the response field names.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
2026-07-29 03:13:16 +00:00
co-authored by Claude Opus 4.8
parent f3dc4415bb
commit ba4503cdd9
-7
View File
@@ -83,13 +83,6 @@ vaultRouter.post('/session/login', async (ctx) => {
clientId,
});
// TEMP diagnostic — field NAMES only (values redacted) to empirically confirm the crypto shape.
const names = (o: unknown) => (o && typeof o === 'object' ? Object.keys(o as object) : typeof o);
const udo = (d as { UserDecryptionOptions?: { MasterPasswordUnlock?: unknown } }).UserDecryptionOptions;
console.log(
`[vault] connect/token fields: ${Object.keys(d).join(',')} | UserDecryptionOptions=${JSON.stringify(names(udo))} | MasterPasswordUnlock=${JSON.stringify(names(udo?.MasterPasswordUnlock))} | AccountKeys=${JSON.stringify(names((d as { AccountKeys?: unknown }).AccountKeys))}`,
);
// Everything except the transport tokens (which the platform holds) is crypto material the SDK unlocks
// on-device — ciphertext to us. Vaultwarden returns BOTH classic (Key/PrivateKey/Kdf*) and v2
// (UserDecryptionOptions.MasterPasswordUnlock, AccountKeys); pass the whole native response through