From d10d3189763ce68a66ddd9879994ae6257deb36d Mon Sep 17 00:00:00 2001 From: Eugene Date: Sun, 14 Aug 2022 13:20:50 +0200 Subject: [PATCH] Created HTTP targets on separate domains (markdown) --- HTTP-targets-on-separate-domains.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 HTTP-targets-on-separate-domains.md diff --git a/HTTP-targets-on-separate-domains.md b/HTTP-targets-on-separate-domains.md new file mode 100644 index 0000000..7ab9300 --- /dev/null +++ b/HTTP-targets-on-separate-domains.md @@ -0,0 +1,21 @@ +> 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: + +```diff + - name: gitlab + allow_roles: + - "warpgate:admin" + - qa + http: + url: http://10.0.0.2 ++ external_host: gitlab.wg.acme.inc +``` \ No newline at end of file