Notifications
Clear all
Topic starter
08/07/2026 7:08 pm
TL;DR: Resilient password management depends on shared database state, database-backed sessions, replicated configuration, and consistent certificate handling across three nodes, according to PassBolt. For identity teams, availability is not just infrastructure hardening; it is lifecycle discipline for the secrets and session state that keep credential access usable.
NHIMG editorial — based on content published by Passbolt: How to Set-Up a Highly-Available Passbolt Environment
Questions worth separating out
Q: How should teams scale a password vault without breaking user sessions?
A: Teams should move session state into a shared backend before adding nodes behind a load balancer.
Q: When does high availability turn into a configuration governance issue?
A: It becomes a governance issue the moment every node must present the same trust material and application behaviour.
Q: How do security teams know a Galera cluster is actually healthy?
A: Security and platform teams should verify cluster membership, replication consistency, and node parity rather than assuming that a service restart succeeded.
Practitioner guidance
- Centralize session storage before scaling out Move application sessions into a shared database so any Passbolt node can continue an authenticated workflow without relying on local disk state.
- Validate cluster health on every node Check wsrep_cluster_size and replication status after bootstrap, restart, and node replacement so silent split-brain or partial membership does not go unnoticed.
- Replicate identity material alongside data Synchronize passbolt.php, GPG files, JWT assets, and certificates across all nodes with preserved permissions, because requests may land on any server.
What's in the full article
Passbolt's full article covers the operational detail this post intentionally leaves for the source:
- Exact MariaDB and Galera configuration snippets for building the cluster topology
- Step-by-step commands for bootstrapping the first node and adding the remaining nodes
- Healthcheck output and troubleshooting guidance for GPG-related errors
- Load balancer and DNS failover options for routing traffic across the three servers
👉 Read Passbolt's guide to building a highly available password vault →
Passbolt high availability: what IAM teams need to change?
Explore further
08/07/2026 7:32 pm
Availability is part of identity governance, not a separate ops concern. A password vault is a control plane for credentials, so its uptime directly affects authentication, privilege use, and incident response. When the system is down, the organisation has not only lost a tool, it has lost the operational path to secrets needed for access recovery and emergency administration. The practical conclusion is that identity resilience must be measured in service continuity, not just backup existence.
A few things that frame the scale:
- 70% of organisations grant AI systems more access than they would give a human employee performing the exact same job, according to The 2026 Infrastructure Identity Survey.
- Only 44% of organisations have implemented any policies to manage their AI agents, even though 92% agree that governing AI agents is critical to enterprise security.
A question worth separating out:
Q: What should teams coordinate before upgrading a clustered identity service?
A: Teams should coordinate application version changes, database migrations, and configuration replication as one change set. If a node upgrades early, it can apply schema changes or configuration differences that other nodes cannot yet handle, which creates intermittent failures and complicates recovery.
👉 Read our full editorial: Highly available Passbolt means database and session state must move
