Components

a database proxy in jumpwire is comprised of several linked concepts a database configuration, a labeled schema, and authentication parameters collectively they comprise a single database proxy configuration each proxy is configured for a specific database external to jumpwire different databases may have slightly different configuration parameters the credentials provided for this configuration will be used for both setting up jumpwire (migrating data, creating column triggers, etc) and authenticating connections that are proxied through postgresql details for connecting to a postgresql database all fields in the table below are required 178,565 trueleft unhandled content type left unhandled content type left unhandled content type left unhandled content type unhandled content type unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type unhandled content type unhandled content type mysql details for connecting to a mysql database all fields in the table below are required 183,560 false true left unhandled content type left unhandled content type left unhandled content type left unhandled content type unhandled content type unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type unhandled content type unhandled content type there are several known limitations specific to the mysql cli when connecting to jumpwire these limitations do not apply to other client libraries the password prompt will truncate entered text to 79 characters since the generated tokens are longer than that, the token must be specified as password=token and not through the interactive prompt with some versions of the mysql cli, authentication will only succeed when using ssl if you must connect to jumpwire without ssl we recommend using the mariadb cli as a drop in replacement, or a programmatic client library instead here is an example connecting to a locally running database schema as soon as the database configuration is saved, jumpwire will connect and list tables in the database each table is turned into a schema that can have individual fields labeled labels set on the schema are mapped against policies docid\ xepswd3fg htpks0zn7pn to determine whether to apply specific data handling rules for fields without any labels, no changes are made to the data as it flows through jumpwire the example below shows a table named users from the configured postgresql database two fields, last name and ssn , have been assigned the label pii proxy authentication the connection string consists of an identifier for this particular database, a token for authentication which maps to a specific classification, and the host and port of the jumpwire proxy this connection uri is the only change needed in your application configuration to start using jumpwire multiple unique tokens can be generated for each database configuration each connection token can be assigned a different classification to indicate which kinds of unmodified data it can receive