warp-tech/warpgate
1
1
Fork 0
mirror of https://github.com/warp-tech/warpgate.git synced 2024-12-26 01:23:50 +08:00
Code Issues Projects Releases Packages Wiki Activity
Page: HTTP targets on separate domains
Pages
Accessing the admin UI Adding a MySQL target Adding a PostgreSQL target Adding an HTTP target Adding an SSH target Chaining Warpgates together Getting started on Docker Getting started HTTP targets on separate domains Home Installing as a systemd service Log forwarding OTP (2 factor authentication) Protocol support SSO Authentication User authentication and roles Using tickets Warpgate behind a reverse proxy
1 HTTP targets on separate domains
Eugene edited this page 2022-08-14 13:20:50 +02:00
Table of Contents

This feature is available in v0.5+

Instead of using ?warpgate-target= in the URL, you can use multiple domains/hostnames and link each to a specific target.

Accessing Warpgate over HTTP on a specific domain will then automatically select the corresponding target.

For optimal results, you want to host Warpgate on a common higher-level domain (e.g. wg.acme.inc, as set by the external_host config option), with target-specific domains as subdomains of this one (e.g. gitlab.wg.acme.inc) - this will prevent users from having to log in again when switching between domains (Warpgate will set its session cookie for all subdomains).

Linking a target to a domain

Set the http.external_host property on the target config:

  - name: gitlab
    allow_roles:
      - "warpgate:admin"
      - qa
    http:
      url: http://10.0.0.2
+     external_host: gitlab.wg.acme.inc