Bridge v3.0.0: broader access, stronger audit
What’s new
Bridge v3.0.0 gives administrators more control over how users connect and gives audit teams a clearer view of their activity. It adds multiple directory connections, optional platform telemetry, and broader database activity capture, with improvements to session review and deployment isolation.
More control and visibility
- Authenticate across multiple directories. Connect Bridge to several Active Directory domains or LDAP directories. Domain-aware routing selects the directory, and server failover handles unavailable controllers without retrying a rejected password elsewhere. Existing single-directory configurations remain supported.
- Choose how each checkout can connect. Allow native clients, browser access, or both for each checkout, within the protocols enabled by the deployment.
- Keep more activity available for review. Expanded database capture covers prepared queries, bulk operations, and other native requests. SSH input remains available for keystroke review and live oversight. Optional video and GIF conversion runs separately from active session workloads.
- Bring session context into Britive. Optional telemetry sends session events and cluster status without blocking sessions. Session-end recording links still require an authorized Bridge login. Platform ingestion support is required.
- Keep HTTP proxy sessions reliable. Recordings handle compressed responses and survive restarts. WebSocket records summarize connections and traffic volume without retaining message contents. Access ends when the checkout expires or is revoked.
- Try VNC and Oracle betas. Both protocols offer native and browser access for development and testing. They are opt-in, disabled by default, and not production-ready. See VNC beta and Oracle beta for configuration and limits.
Fixes and hardening
This release improves recording recovery, session cleanup, browser errors, and memory use during busy terminal sessions. Logout revocation applies across the cluster, target identity checks are stricter, and internal cluster traffic uses mutual authentication. Spreadsheet exports use safer defaults.
Command filtering and sensitive-data redaction remain best effort. Target-system permissions remain the access boundary.
Plan the upgrade
v3.0.0 is a breaking release. Historical desktop recordings remain readable. Schedule a maintenance window, prepare target certificates and SSH host keys, and upgrade every cluster role together. Users must sign in again after the upgrade. Kubernetes deployments also require Helm chart 3.0.0 and Kubernetes 1.33 or later.