fix(passbolt): disable metadata encryption for new instance setup
Passbolt 5.x's isNotCreatedInTheFutureRule has zero tolerance for clock skew — even 1 second between browser and server causes the metadata key creation to fail during first setup. Disabling the automatic metadata setup for new instances allows the browser extension to complete account setup successfully. Encrypted metadata can be enabled from the admin panel post-setup. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
1 parent
758e69300f
commit
6f12bf9af7
1 file changed
+1
@@ -7,6 +7,7 @@ services:
|
|||||||
PASSBOLT_SSL_FORCE: "false"
|
PASSBOLT_SSL_FORCE: "false"
|
||||||
TZ: ${TIMEZONE:-Europe/Amsterdam}
|
TZ: ${TIMEZONE:-Europe/Amsterdam}
|
||||||
PASSBOLT_REGISTRATION_PUBLIC: "false"
|
PASSBOLT_REGISTRATION_PUBLIC: "false"
|
||||||
|
PASSBOLT_PLUGINS_METADATA_ENABLE_FOR_NEW_INSTANCES: "false"
|
||||||
DATASOURCES_DEFAULT_HOST: passbolt_db
|
DATASOURCES_DEFAULT_HOST: passbolt_db
|
||||||
DATASOURCES_DEFAULT_PORT: "5432"
|
DATASOURCES_DEFAULT_PORT: "5432"
|
||||||
DATASOURCES_DEFAULT_DATABASE: passbolt
|
DATASOURCES_DEFAULT_DATABASE: passbolt
|
||||||
|
|||||||
Reference in new issue
Block a user