Closed ammarfaris closed 7 months ago
That's probably related to these two changes:
Basically the URL for the oauth callback is now constructed automatically from both the Host header and the API prefix (which also removes the need for path rewrites) so you will probably need to change your load balancer configuration and migrate from path rewrites to AUTH_API_PREFIX in order to upgrade.
That's probably related to these two changes:
- 024258c: feat: set oauth origin dynamically based on host header
- 5663eec: feat: allow configuring api prefix
Basically the URL for the oauth callback is now constructed automatically from both the Host header and the API prefix (which also removes the need for path rewrites) so you will probably need to change your load balancer configuration and migrate from path rewrites to AUTH_API_PREFIX in order to upgrade.
okay appreciate your explanation. it works now with latest 0.24.0, following your guidance 🙏🏻
Closing now. thanks @dbarrosop
In hasura-auth 0.20.2, when I set
AUTH_SERVER_URL=https://api.mydomain.com/v1/auth
, the redirect uri generated by hasura-auth for google provider follows AUTH_SERVER_URL =>https://api.mydomain.com/v1/auth/signin/provider/google/callback
...but in the latest hasura-auth 0.24.0, even when I set
AUTH_SERVER_URL=https://api.mydomain.com/v1/auth
, the redirect uri generated by hasura-auth ishttps://api.mydomain.com/signin/provider/google/callback
without/v1/auth
When i revert back to hasura-auth 0.20.2, the google provider works as intended