-
oauth2-proxy
A reverse proxy that provides authentication with Google, Azure, OpenID Connect and many more identity providers.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
I just recently wrapped up oauth for my personal cluster. My deployed ingress comes from a helm dry-run of https://github.com/kubernetes/ingress-nginx/tree/master/charts/ingress-nginx, which I use in conjunction with a reverse-proxy called oauth2-proxy https://oauth2-proxy.github.io/oauth2-proxy/. The oauth2-proxy ingress uses the annotation: nginx.ingress.kubernetes.io/auth-request-redirect: $request_uri Each ingress, or just one if you decide to secure your routes using a wildcard, should have the following 2 annotations for the oauth magic to work: nginx.ingress.kubernetes.io/auth-url: "https://abc.xyz/oauth2/auth" nginx.ingress.kubernetes.io/auth-signin: "https://abc.xyz/oauth2/start?rd=https://abc.xyz/" The first being where to direct requests after being authenticated and the second being the route to redirect when starting the authentication flow
I've been trying to use https://www.nginx.com/products/nginx-ingress-controller/with https://oauth2-proxy.github.io/oauth2-proxy/. I've been trying to use those annotations that you mention but they do not redirect. Any idea why? Maybe the nginx-ingress-controller from nginx.com just don't support oauth2 proxy.
Related posts
-
Multi client authentication with auth0 and oauth2-proxy
-
Why You Should Migrate to OAuth 2.0 From API Keys
-
Moving from Google workspace to Microsoft 365 and implementing Zero Trust
-
Microsoft launches Windows App for accessing PCs in the cloud from any device
-
Best Practice For Serving Static (Frontend) Files with NGINX in K8s?