docs: add synology tutorial (#79)

docs/.vuepress/config.js

@@ -16,8 +16,10 @@ module.exports = {
 		docsDir: "docs",
 		editLinkText: "Edit this page on GitHub",
 		lastUpdated: "Last Updated",
-		nav: [{ text: "Quick Start", link: "/guide/" },
-		{ text: "Documentation", link: "/docs/" }],
+		nav: [
+			{ text: "Quick Start", link: "/guide/" },
+			{ text: "Documentation", link: "/docs/" }
+		],
 		sidebar: {
 			"/guide/": guideSidebar("Quick Start"),
 			"/docs/": docsSidebar("Documentation")
@@ -30,7 +32,7 @@ function guideSidebar(title) {
 		{
 			title,
 			collapsable: false,
-			children: ["", "helm", "kubernetes", "from-source"]
+			children: ["", "helm", "kubernetes", "synology", "from-source"]
 		}
 	];
 }

docs/guide/synology.md

@@ -0,0 +1,225 @@
+# Synology
+
+Pomerium can be used to enable secure access to services on your Synology home server or network attached storage (NAS) device. Pomerium acting as an identity aware access proxy is particularly useful as many [self-hosted apps] lack or have insufficient built-in authentication mechanisms.
+
+Using Pomerium on your Synology DSM device enables:
+
+- Secure remote access to docker and synology web-applications without a VPN.
+- Unified, multi-factor authentication with your identity provider of choice.
+- Access to services by sub-domain (e.g. `plex.int.nas.example.com` or `wiki.int.nas.example.com`)
+- TLS everywhere.
+
+Pomerium is lightweight, can easily handle hundreds of concurrent requests, and a single instance typically uses <20MB of memory and very little CPU.
+
+## Prerequisites
+
+- A [docker-capable] synology product
+- A [Google Cloud Account](https://console.cloud.google.com/)
+- A configured Google OAuth2 [identity provider]
+- A wild-card TLS certificate
+
+Though any supported identity provider would work, this guide uses google.
+
+## Port forwarding
+
+This will vary depending on what type of router you have but the gist is you want to be forwarding all HTTPS/TLS traffic from port `443` to your NAS on some high port (in this case`8443`).
+
+![Synology configure firewall rules](./synology/synology-firewall-rules.png)
+
+## DSM
+
+[Diskstation manager] uses [nginx] under-the-hood to proxy incoming requests. In the following steps, we'll configure DSM to handle incoming requests and certificates. 
+
+### Configure DSM's Reverse Proxy
+
+Go to **Control Panel** > **Application Portal** > **Reverse Proxy**.
+
+Click **Create**.
+
+Set the following **Reverse Proxy Rules**. 
+
+Field                | Description
+-------------------- | -----------
+Description          | pomerium
+Source Protocol      | HTTPS
+Source Hostname      | *
+Destination Port     | 8443
+HTTP/2               | Enabled
+HSTS                 | Enabled
+Destination Protocol | HTTPS
+Destination Hostname | localhost
+Destination Port     | 32443
+
+![Synology setup nginx reverse proxy](./synology/synology-reverse-proxy.png)
+
+This will forward any incoming HTTPS traffic to the Pomerium service that is (not yet) running on port **32433**.
+
+### Certificates
+
+Though DSM does support getting [LetsEncrypt] certificates, they do not support wild-card subdomain certificates which require DNS validation. Hopefully you have one handy, or you used the included [script] to get one.
+
+Go to **Control Panel** > **Security** > **Certificate**
+
+Click **add a new certificate** > **Import certificate**.
+
+Add the certificate chain for your wild-card subdomain certificates.
+
+Once the certificate is showing on the list of certificates screen we need to tell DSM to use that certificate for all incoming traffic on port **8443**.
+
+**Click configure**
+
+Services | Certificate
+-------- | -----------------------
+*:8443   | `*.int.nas.example.com`
+
+
+![Synology assign wildcard certificate](./synology/synology-certifciate-assignment.png)
+
+## Docker
+
+### Download
+
+Download and install docker from the package manager.
+
+**Package manager** > **search** > **docker**
+
+![Synology download pomerium docker image](./synology/synology-docker-package-center.png)
+
+Once installed open the docker app.
+
+**Docker** > **Registry** > **search** > **pomerium**
+
+**Download** the official Pomerium docker image.
+
+![Synology download pomerium docker image](./synology/synology-docker-pomerium-package.png)
+
+We'll also need a test application to manage access to. For this guide we'll use the canonical test app [httpbin] but the this could be any [self-hosted apps], wiki, download tool, etc.
+
+![Synology download httpbin docker image](./synology/synology-httpbin.png)
+
+### Policy
+
+We will create an extremely basic policy where `httpbin.int.nas.example.com` is replaced with the subdomain you want to use for the httpbin service, and `your.email.address@gmail.com` is replaced with your email address. All other users will be denied, and all other routes will be `404`.
+
+```yaml
+# policy.yaml
+- from: httpbin.int.nas.example.com
+  to: http://httpbin
+  allowed_users:
+  - your.email.address@gmail.com
+```
+
+### Configure
+
+#### Httpbin
+
+First, we'll setup our test app [httpbin].
+
+Go to **Docker** > **Image**
+
+Click **httpbin**
+
+Set the **Container Name** to `httpbin`. Keep the rest of the settings the default.
+
+Click **apply**
+
+![Synology launch httpbin](./synology/synology-docker-httpbin.png)
+
+This will create a small python webserver on port 80\. The container name we just used will be used as an alias to route requests as defined in our policy.
+
+#### Pomerium
+
+Go to **Docker** > **Image**
+
+Click **Pomerium**
+
+Click **Launch**
+
+Set the **Container Name** to `Pomerium`.
+
+![Synology pomerium create container](./synology/synology-docker-pomerium-create-container.png)
+
+Click **Advanced Settings**
+
+Go to **Port Settings** tab.
+
+Add an entry where the **Local Port** is **32433** and the container port is **443** and the type is **TCP**.
+
+![Synology pomerium port settings docker](./synology/synology-docker-port-settings.png)
+
+Go to **Links** tab.
+
+Add an entry where the **Container Name** is `httpbin` and the **alias** is `httpbin`.
+
+::: warning
+
+The alias value must match the `to` DNS name from your policy.yaml configuration.
+
+:::
+
+![Synology pomerium set alias to app](./synology/synology-docker-pomerium-alias.png)
+
+These are the minimum set of configuration settings to get Pomerium running in this deployment environment.
+
+Go to **Environment** tab.
+
+Field                     | Value
+------------------------- | ---------------------------------------------------------------
+POLICY                    | output of `base64 -i policy.yaml`
+CERTIFICATE               | output of `base64 -i *.int.nas.example.com.cer`
+CERTIFICATE_KEY           | output of `base64 -i *.int.nas.example.com.key`
+CERTIFICATE_AUTHORITY     | output of `base64 -i ca.cer`
+OVERRIDE_CERTIFICATE_NAME | `*.int.nas.example.com`
+IDP_CLIENT_SECRET         | Values from setting up your [identity provider]
+IDP_CLIENT_ID             | Values from setting up your [identity provider]
+IDP_PROVIDER              | Values from setting up your [identity provider] (e.g. `google`)
+REDIRECT_URL              | `https://authenticate.int.nas.example.com/oauth2/callback`
+COOKIE_SECRET             | output of `head -c32 /dev/urandom | base64`
+SHARED_SECRET             | output of `head -c32 /dev/urandom | base64`
+PROXY_ROOT_DOMAIN         | `int.nas.example.com`
+AUTHORIZE_SERVICE_URL     | `https://authorize.int.nas.example.com`
+AUTHENTICATE_SERVICE_URL  | `https://authenticate.int.nas.example.com`
+AUTHORIZE_INTERNAL_URL    | `localhost:443`
+AUTHENTICATE_INTERNAL_URL | `localhost:443`
+
+For a detailed explanation, and additional options, please refer to the [configuration variable docs].
+
+Click **Launch**.
+
+If properly configured you should see something like the following when you see the container's details.
+
+![Synology pomerium all setup](./synology/synology-docker-pomerium-done.png)
+
+If something goes wrong, click the **Logs** tab.  
+
+
+## Try it out
+
+Navigate to your new service. `https://httpbin.int.nas.example.com` 
+
+You should be redirected to your identity provider. 
+
+![Synology redirected login](./synology/synology-step-1-redirect.png)
+
+If you've enabled multi-factor authentication you should see that too. 
+
+![Synology multifactor authentication](./synology/synology-step-2-mfa.png)
+
+If that user is authorized to see the httpbin service, you should be redirected back to httpbin!
+
+![Synology done](./synology/synology-step-3-validate-header.png)
+
+And just to be safe, try logging in from another google account to see what happens. You should be greeted with a `403` unauthorized access page. 
+
+![Synology done](./synology/synology-step-4-unauthorized.png)
+
+
+[configuration variable docs]: ../docs/config-reference.html
+[diskstation manager]: https://www.synology.com/en-us/dsm
+[docker-capable]: https://www.synology.com/en-us/dsm/packages/Docker
+[httpbin]: https://httpbin.org
+[identity provider]: ../docs/identity-providers.md#google
+[letsencrypt]: https://letsencrypt.org/
+[nginx]: https://www.nginx.com
+[script]: https://github.com/pomerium/pomerium/blob/master/scripts/generate_wildcard_cert.sh
+[self-hosted apps]: https://github.com/Kickball/awesome-selfhosted