meutel/oauth2_proxy
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
Fork https://github.com/pusher/oauth2_proxy.git Adding gitea provider
4 Commits 6 Branches 12 Tags 1.8 MiB
Go 98%
Makefile 1.3%
Shell 0.4%
Dockerfile 0.3%
4861cb8e65
Go to file
Jehiah Czebotar 4861cb8e65 update readme
2012-12-17 13:03:34 -05:00
.gitignore initial code import 2012-12-10 20:59:23 -05:00
cookies.go initial code import 2012-12-10 20:59:23 -05:00
htpasswd.go initial code import 2012-12-10 20:59:23 -05:00
main.go initial code import 2012-12-10 20:59:23 -05:00
oauthproxy.go initial code import 2012-12-10 20:59:23 -05:00
README.md update readme 2012-12-17 13:03:34 -05:00
string_array.go initial code import 2012-12-10 20:59:23 -05:00
templates.go initial code import 2012-12-10 20:59:23 -05:00
validator.go initial code import 2012-12-10 20:59:23 -05:00

README.md

google_auth_proxy

A reverse proxy that provides authentication using Google OAuth2 to validate individual accounts, or a whole google apps domain.

Structure

    _______       ___________________       __________
    |Nginx| ----> |google_auth_proxy| ----> |upstream| 
    -------       -------------------       ----------
                          ||
                          \/
                  [google oauth2 api]

Configuration

  1. visit to Google Api Console https://code.google.com/apis/console/
  2. under "API Access", choose "Create an OAuth 2.0 Client ID"
  3. Edit the application settings, and list the Redirect URI(s) where you will run your application. For example: https://internalapp.yourcompany.com/oauth2/callback

Usage

Usage of ./google_auth_proxy:
  -authenticated-emails-file="": authenticate against emails via file (one per line)
  -client-id="": the Google OAuth Client ID: ie: "123456.apps.googleusercontent.com"
  -client-secret="": the OAuth Client Secret
  -cookie-domain="": an optional cookie domain to force cookies to
  -cookie-secret="": the seed string for secure cookies
  -google-apps-domain="": authenticate against the given google apps domain
  -htpasswd-file="": additionally authenticate against a htpasswd file. Entries must be created with "htpasswd -s" for SHA encryption
  -http-address="0.0.0.0:4180": <addr>:<port> to listen on for HTTP clients
  -pass-basic-auth=true: pass HTTP Basic Auth information to upstream
  -redirect-url="": the OAuth Redirect URL. ie: "https://internalapp.yourcompany.com/oauth2/callback"
  -upstream=[]: the http url(s) of the upstream endpoint. If multiple, routing is based on path
  -version=false: print version string

Unauthenticated requests will be redirected to /oauth2/sign_in to start the sign-in process.

Example

To run google_auth_proxy as a reverse proxy on port 4180 authenticating requests for an application running on port 8080 at internal.yourcompany.com you would use

./google_auth_proxy \
   --redirect-url="https://internal.yourcompany.com/oauth2/callback"  \
   --google-apps-domain="yourcompany.com"  \
   --upstream=http://127.0.0.1:8080/ \
   --cookie-secret=... \
   --client-id=... \
   --client-secret=...

An example Nginx config to listen on ssl (port 443) and forward requests to port 4180 would be

server {
    listen 443 default ssl;
    server_name internal.yourcompany.com;
    ssl_certificate /path/to/cert.pem;
    ssl_certificate_key /path/to/cert.key;
    add_header Strict-Transport-Security max-age=1209600;

    location / {
        proxy_pass http://127.0.0.1:4180;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Scheme $scheme;
        proxy_connect_timeout 1;
        proxy_send_timeout 30;
        proxy_read_timeout 30;
    }
}