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.
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.
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’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:
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: