nginx-openid-connect VS lua-resty-openidc

Could you please suggest an OIDC filter/side-car which is capable of configure it with a custom IDP? Nginx Plus has a OIDC filter https://github.com/nginxinc/nginx-openid-connect and looking for a similar solution. I am planning to use AKS for api and Web compute. Thanks!

> With both Apache and Nginx you can let the web server do all the OpenID Connect work for you for paths you specify.

Seems like at least the official nginx solution for this requires their paid subscription: https://github.com/nginxinc/nginx-openid-connect

Got any tips for how to do it with their open-source solution?

It's not a matter of better or worst security than Traefik or NGINX, it's that if you do not have entreprise level licence for those software, you don't actually have the security modules that protect your services (ex. https://www.nginx.com/products/nginx/) Cosmos includes a WAF by default without subscription

You can scale up it with side car pattern with K8. One product you can use is https://github.com/nginxinc/nginx-openid-connect and if you Azure they have a built in capability as well. I haven't worked with AWS for a while but probably they will have an equal solution.

You could purchase NGINX Plus which allows many things to be configured via API calls.

If you have an active Nginx plus subscription the OIDC implementation will help. https://github.com/nginxinc/nginx-openid-connect

There's an nginx Lua build that can do it on nginx through a Lua module: https://github.com/zmartzone/lua-resty-openidc

Apache is a lot easier to configure, though.

Yes, I believe the way to do it with the free version is to use this: https://github.com/zmartzone/lua-resty-openidc

You'd have to be careful with custom code like this, though, because it's very easy to try to get the server to send a redirect but end up sending actual content that just has its HTTP status code changed to 301. The example seems to fail with 500 instead of redirecting, that's one way to do it.