website logo
⌘K
JumpWire Overview
Database Proxy
API Gateway
Concepts
Policies
Classifications
Databases
Clusters
Deployment
Self-hosting with AWS ECS
Self-hosting with Docker
Self-hosting with Helm
Components
Vault Integration
Configuration
Observability
Encryption key stores
Encryption format
Architecture
Docs powered by archbee 
7min

Deployment

The default distribution for JumpWire is through Docker containers. There are two containers published by JumpWire, one for the control web application and one for the execution engine. Additional containers may also be necessary to implement functionality depending on the cloud environment JumpWire is installing into.  See the Components page for details.

IaC templates for popular container orchestration services (Helm, Terraform, CloudFormation, etc) are available by request. The JumpWire team is happy to work hands-on to ensure a seamless and scalable deployment during onboarding.

Environments

Kubernetes

In addition to cloud container runtimes, JumpWire is compatible with self-hosted Kubernetes environments. The deployment team can provide Helm charts to assist with installation.

Authentication

JumpWire supports any OAuth or OpenID providers for authenticating to the web frontend with client credentials configured during setup.

If your preferred provider is not listed below, let us know and will add it.

Google OAuth

Google’s Single Sign On for OAuth authentication. The OAuth client is tied to an installation’s domain name (for callbacks) and a customer’s email domain (for identity verification).

You can read more about provisioning Google OAuth applications at this support page.

When using Google OAuth, the following Configuration variables must be set:

  • JUMPWIRE_AUTH_DOMAINS
  • GOOGLE_CLIENT_ID
  • GOOGLE_CLIENT_SECRET

Auth0

Details on setting this up a new Auth0 application are available in Auth0's documentation. The application should be a "Regular Web Application" with these settings:

  • Allowed Callback URL: https://JUMPWIRE_DOMAIN/auth/auth0/callback
  • Allowed Logout URL: https://JUMPWIRE_DOMAIN
  • Allowed Web Origins: https://JUMPWIRE_DOMAIN
  • Allowed Origins (CORS): https://JUMPWIRE_DOMAIN
  • Under Advanced > OAuth:
    • JSON Web Token (JWT) Signature Algorithm: RS256
    • OIDC Conformant: toggled on

When using Auth0, the following Configuration variables must be set:

  • AUTH0_DOMAIN
  • AUTH0_CLIENT_ID
  • AUTH0_TOKEN_SECRET



Updated 03 Mar 2023
Did this page help you?
Yes
No
UP NEXT
Self-hosting with AWS ECS
Docs powered by archbee 
TABLE OF CONTENTS
Environments
Kubernetes
Authentication
Google OAuth
Auth0