Mr-EmPee opened a new issue, #12970: URL: https://github.com/apache/apisix/issues/12970
### Current Behavior Starting from Apache APISIX 3.14.0, the openid-connect plugin generates redirect / callback URLs without the original request port, even when the client accesses APISIX directly (no reverse proxy or load balancer in front). The same configuration works correctly on APISIX 3.13.0, where the redirect URL preserves the port. This is a regression and breaks OIDC flows when APISIX is exposed on a non-default port (anything other than 80/443). **Actual behavior** ```bash $ curl -v http://localhost:8888 2>&1 | grep -i '< Location' < Location: http://10.126.166.49:8888/auth/realms/warehouse-automation/protocol/openid-connect/auth?scope=openid%20profile&client_id=apisix&redirect_uri=**http%3A%2F%2Flocalhost%2F.apisix**%2Fredirect&state=f44c18832740fc4486c099a6be0c1329&response_type=code ``` As you can see the redirect_uri parameter is missing the original request port ### Expected Behavior ```bash $ curl -v http://localhost:8888 2>&1 | grep -i '< Location' < Location: http://10.126.166.49:8888/auth/realms/warehouse-automation/protocol/openid-connect/auth?state=d15ffd15ae044c3d0f1c0583ce9f203e&response_type=code&scope=openid%20profile&redirect_uri=http%3A%2F%2F**localhost%3A8888**%2F.apisix%2Fredirect&client_id=apisix ``` ### Error Logs _No response_ ### Steps to Reproduce 1. Run APISIX 3.14.0+ on port 8888 and configure OIDC plugin 2. Try to make a curl to a protected route ### Environment - APISIX: 3.1.1-debian -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
