The Britive Bridge is a self-hosted proxy that sits between your users and the systems they need to reach, such as Linux and Windows servers, databases, Kubernetes clusters, network devices, and internal web applications. Every connection flows through the Bridge, which grants just-in-time access, records the full session, and hands the recording back to your security and audit teams.
Britive Bridge has the following key features:
Just-in-time access: Users connect through the bridge instead of holding standing credentials on the target system. Access is granted for a checkout window and automatically revoked when it ends.
Two ways to connect: Users can connect with the native client tools they already know (the
sshcommand, a database CLI, or Microsoft Remote Desktop) or do everything inside the web browser with nothing to install.Full session recording: Terminal sessions, desktop sessions, database queries, and web traffic are recorded for playback and audit, with secrets automatically masked.
Live oversight: Authorized reviewers can watch active sessions and lock or disconnect them midstream.
Configuring Bridge Attributes
Log in to the Britive portal.
Click Manage Account from the upper-right user icon.
Click Bridge Attributes.
Click Edit to configure the following bridge attributes:
Bridge Username: The username used to authenticate to the target server.
Bridge Password: The password associated with that username.
Bridge SSH Key: An SSH public key used as an alternative to password-based authentication. Bridge SSH keys cannot be edited; you can delete the existing key and enter a new one. Britive accepts the following SSH public key types:
Ed25519
RSA
ECDSA
Attribute
Purpose
Validation
Bridge Username
Login name for the target server
None
Bridge Password
Password for the target server
Tenant password policy
Bridge SSH Key
SSH public key for key-based authentication
Valid key type and format