Have a static documentation website but may have sensitive information that you only want to expose to a certain group of people? This tool is for you!
Secured your static website with different oauth provider with ease, deploy to anywhere that support Docker.
oauth2_proxy is a reverse proxy and static file server that provides authentication using Providers (Google, Github, and others) to validate accounts by email, domain or group.
This project provides a Dockerfile and a oauth2_proxy.cfg to make it easier for you deploy to any platform that support Docker deployment.
- Clone the repo to your local
$ git clone git@github.com:fraserxu/secured-static-land.git-
Put your documentation or static file inside
/staticfolder, this can be any static website or files generated by React.js, Vue.js or markdown files. -
Update
oauth2_proxy.cfgto configprovider,email domains. For more details please check oauth2_proxy.sample.cfg.
Import notes: Please do not put client_id, client_secret or any sensitive information in your source code,
you can pass it through environment variables instead.
The following environment variables can be used in place of the corresponding command-line arguments:
OAUTH2_PROXY_CLIENT_IDOAUTH2_PROXY_CLIENT_SECRETOAUTH2_PROXY_COOKIE_NAMEOAUTH2_PROXY_COOKIE_SECRETOAUTH2_PROXY_COOKIE_DOMAINOAUTH2_PROXY_COOKIE_EXPIREOAUTH2_PROXY_COOKIE_REFRESHOAUTH2_PROXY_SIGNATURE_KEY
Make sure you have a working Docker installation (eg. docker ps) and that you’re logged in to Heroku (heroku login).
Install the container-registry plugin by running:
$ heroku plugins:install heroku-container-registryLog in to the Heroku container registry:
$ heroku container:loginCreate a heroku app from command line:
$ heroku createBuild the image and push to the Heroku container registry:
$ heroku container:push webNow open the app in your browser:
$ heroku openLast but not least, go to the settings page of you app and put the required environment variables to the Config Vars section.
🎉
MIT