- Rename SessionState to State to avoid stutter. - Simplified option validation to use a wrapper function for base64 secrets. - Removed authenticates grpc code. - Abstracted logic to load and validate a user's authenticate session. - Removed instances of url.Parse in favor of urlutil's version. - proxy: replaces grpc refresh logic with forced deadline advancement. - internal/sessions: remove rest store; parse authorize header as part of session store. - proxy: refactor request signer - sessions: remove extend deadline (fixes #294) - remove AuthenticateInternalAddr - remove AuthenticateInternalAddrString - omit type tag.Key from declaration of vars TagKey* it will be inferred from the right-hand side - remove compatibility package xerrors - use cloned http.DefaultTransport as base transport |
||
---|---|---|
.. | ||
img | ||
binary.md | ||
helm.md | ||
kubernetes.md | ||
readme.md | ||
synology.md |
title | lang | meta | |||||
---|---|---|---|---|---|---|---|
Docker | en-US |
|
Pomerium using Docker
In the following quick-start, we'll create a minimal but complete environment for running Pomerium with containers.
Prerequisites
- A configured identity provider
- Docker and docker-compose
- A wild-card TLS certificate
Configure
Configuration file
Create a configuration file (e.g config.yaml
) for defining Pomerium's configuration settings, routes, and access-policies. Consider the following example:
<<< @/docs/docs/reference/examples/config/config.minimal.yaml
Ensure the docker-compose.yml
contains the correct path to your config.yaml
.
Docker-compose
Download the following docker-compose.yml
file and modify it to:
- generate new secrets
- mount your wild-card TLS certificate
- mount your
config.yaml
configuration file
<<< @/docs/docs/reference/examples/docker/basic.docker-compose.yml
Run
Finally, simply run docker compose.
docker-compose up
Docker will automatically download the required container images for Pomerium and httpbin. Then, Pomerium will run with the configuration details set in the previous steps.
You should now be able access to the routes (e.g. https://httpbin.corp.yourdomain.example
) as specified in your policy file.