A JFrog Bridge connects a Bridge Server JPD to a Bridge Client JPD:
- SaaS JPDs act as Bridge Servers. Contact JFrog Customer Success to verify that the Bridge service is enabled for JPDs in your SaaS environment.
- Self-managed JPDs act as Bridge Clients. You must install the Bridge Client service on these JPDs.
The Bridge Client establishes a persistent, outbound TCP connection to the Bridge Server with an HTTP Upgrade request. This creates a secure tunnel compatible with corporate firewalls. The Bridge Client service initiates new independent TCP tunneling sessions to the Bridge Server as traffic demands, within configurable ranges.
A registration token secures the Bridge connection. JSON Web Tokens (JWTs) authenticate forwarded API requests. Authentication uses your self-managed environment's custom CA certificates.
Resilient, auto-scaling topologies are easily created:
- Bridges are typically grouped in a one-to-many architecture: a single SaaS Bridge Server securely communicates with Bridge Clients on multiple, independent Self-managed JPDs.
- To support High Availability, multiple nodes of the Bridge Client and Server services can be created.
For more information, see JFrog Bridge feature and use case documentation.