I'm having trouble with JWT authentication on my Application Load Balancer (ALB). Even though I've set it up with a different host header, a sub-path, and placed it at the end of my rules, it's still blocking callbacks to /oauth2/idpresponse. The moment I remove that last rule, OIDC authentication works again. Has anyone else faced this problem?
2 Answers
It sounds like you're wrestling with rule conflicts on your ALB. What specific rule are you trying to implement that keeps interfering with OIDC? Sometimes, it’s all about the order of operations, but if removing that last rule solves your issue, it makes you wonder if there's a deeper bug. Just to clarify, are you able to share the relevant rule configuration?
Yeah, I've run into similar issues before! It can be frustrating when seemingly valid setups don’t work as expected. Based on what you described, it does sound like it could be a bug in the way the ALB is processing the rules. Have you considered moving your API access to API Gateway, or are you hoping to keep everything under the ALB for consistency?
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