oauth-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 chart bootstraps a oauth-proxy deployment on a Kubernetes cluster using the Helm package manager.

Note – at this time, there is a known incompatibility between oauth-proxy version 2.2 (which is it’s latest release) and nginx-ingress versions >= 0.9beta12. To utilize this chart at this time please use nginx-ingress version 0.9beta11

 

You will need to register an OAuth application with a Provider (Google, GitHub or another provider), and configure it with Redirect URI(s) for the domain you intend to run oauth2_proxy on.

Valid providers are :

  • Google default
  • Azure
  • Facebook
  • GitHub
  • GitLab
  • LinkedIn

The provider can be selected using the provider configuration value.

 

 

Related

redis-ha

Redis ha

Recently, at the place where I work, we started to use Redis for session-like… 

  • 4.4K

buzzfeed sso

Heavily inspired by Buzzfeed’s example, this provides a way of protecting… 

  • 259

SignalSciences

SignalSciences is a hosted web application firewall. 

  • 3.8K

Tell us about a new Kubernetes application

Newsletter

Never miss a thing! Sign up for our newsletter to stay updated.

About

Discover and learn about everything Kubernetes

Navigation
Follow

Submit