Getting Started
PrivMX Bridge
Server-side software that intermediates in the transfer of encrypted data and notifications between Endpoints and stores encrypted data for Threads, Stores, and Inboxes.
-
PrivMX Bridge is a Zero-Knowledge software - it has no possibility of reading (decrypting) data it transmits and stores.
-
The Bridge organizes the structure of the developer's applications (Solutions) by offering a universal mechanism of independent access groups called Contexts. Each Context is a set of communication tools (Threads, Stores, Inboxes created by Endpoints) together with a list of users that have rights to create and access them. Each Solution can contain any number of freely configurable Contexts.
-
User’s registration in PrivMX Bridge Contexts requires providing only user’s public key and any textual userId assigned by the application. As a result, PrivMX communication channels can be easily used in existing applications, with no necessary changes to the authorization system currently in use. To learn more about private and public keys, browse our dedicated section.
-
In short: the user's access to a Context and the tools included is granted after the Bridge (using a registered public key) successfully verifies the user's signature sent by the Endpoint (signature made on the client-side with the valid, corresponding private key).
-
Bridge offers a web API and a system of developer keys, so that Solutions and Context objects can be managed programmatically by any developer’s tools and applications.
For more guidance with using PrivMX Bridge, go to Bridge API documentation.
Installation
To install Bridge on your machine you can use our CLI.
- Clone Bridge CLI
git clone https://github.com/simplito/privmx-bridge-docker
- Run setup script
This will fetch the necessary Docker images, create Access Keys and your first Context. After a successful setup, CLI will display all the API keys necessary for connection.
./setup.sh