A reverse proxy and static file server that provides OAuth2 authentication for arm32v7 platform
302
This is a Dockerization of the bitly OAuth Proxy for arm32v7.
Check out the bitly github page for more details on the different command line options that can be passed in.
Dockerfile linkslatestFirst, configure your client secret/id/cookie secret in the docker-compose.yml file and replace all references to example.com with your domain.
Then simply run:
docker-compose up
The container will be built and an nginx proxy automatically configure to connect to the oauth2 proxy. Navigate to http://(docker ip)/ping to check out whether the proxy is up a
You will be asked to authenticated and if successful, redirected to the upstream nginx container serving a simple HTML page.
The following example assumes you have your upstream host located at upstream:80
docker run -P dbabesh/oauth2_proxy \
--cookie-secure=false \
--upstream="http://upstream:80" \
--http-address="0.0.0.0:4180" \
--redirect-url="http://example.com/oauth2/callback" \
--email-domain="example.com" \
--cookie-secret=<cookie-secret> \
--client-id=<client-id> \
--client-secret=<client-secret>
By default I set the upstream and http-address to the following:
--upstream=http://0.0.0.0:8080/
--http-address=0.0.0.0:4180
This allows us to easily configure our upstream or nginx proxy to those addresses.
Alternatively you can set the cookie-secret, client-id, and/or client-secret as environment variables using the following variables below:
OAUTH2_PROXY_COOKIE_SECRET # The seed string for secure cookies
OAUTH2_PROXY_CLIENT_ID # The Google OAuth Client ID
OAUTH2_PROXY_CLIENT_SECRET # The Google OAuth Client Secret
docker run -e OAUTH2_PROXY_COOKIE_SECRET=<cookie-secret> \
-e OAUTH2_PROXY_CLIENT_ID=<client-id> \
-e OAUTH2_PROXY_CLIENT_SECRET=<client-secret> \
dbabesh/oauth2_proxy
Content type
Image
Digest
Size
35.7 MB
Last updated
over 8 years ago
docker pull dbabesh/oauth2_proxy