I'm currently using ingress-nginx, which is now deprecated, and I'm thinking about moving to an API Gateway. From what I understand, it seems that none of the Envoy-based API gateways, like the Envoy API Gateway and KGateway, support OAuth2 client credentials flow for protecting the upstream or backend. However, I've noticed that NGINX/OpenResty-based API Gateways, such as Apache APISIX and Kong, do support this type of authorization. I'm also considering go-based API Gateways like KrakenD and Tyk. Is that assessment accurate?
1 Answer
Just a heads-up, your terms are a bit mixed up. An API Gateway is different from a Gateway API. The API Gateway isn’t really about routing or managing auth — that's typically where you'd set up something like OAuth2 Proxy to handle that job. It’s important to keep those roles distinct!
Related Questions
How To: Running Codex CLI on Windows with Azure OpenAI
Set Wordpress Featured Image Using Javascript
How To Fix PHP Random Being The Same
Why no WebP Support with Wordpress
Replace Wordpress Cron With Linux Cron
Customize Yoast Canonical URL Programmatically