Your session, your key
Control compact-session encryption through configuration, an environment variable or a mounted Docker secret.
Developers and operators
OpenWA 5.4 adds your own compact-session encryption key. Set sessionDataEncryptionKey, use OPENWA_SESSION_DATA_ENCRYPTION_KEY, or mount a secret through sessionDataEncryptionKeyFile. Omit these settings to use the baked default.
const client = await create({ sessionId: 'sales', sessionDataEncryptionKeyFile: '/run/secrets/openwa-session-key',});Supply a base64-encoded 32-byte key. Keep the same key and session ID when moving the compact session between containers, and store the key separately from the saved file. Compact authentication is the current path; moving from a browser profile or changing keys requires fresh pairing.
Key settings are redacted from diagnostics and startup events. Verbose environment logs show names only. Existing filename, path and S3 configuration remain available, but live browser/S3 acceptance for this integration was unverified at release. Companion packages align to 5.4.0 without separate feature changes.
Use the current session storage guide and quickstart for a new deployment.