-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Imperial Beta release: Google completion handler not called #115
Comments
Trying it myself it seems like With the full URL I get a 404 when querying |
In the latest beta we switched from custom path components handling to RoutingKit, so it must be that. |
On the bright side you should now not need the environment variable anymore as you can pass the path directly to it and it will be valid for development and production. I think this is why the Kodeco book used environmental variables, and not for security reasons, but I'm not 100% sure. |
Seems Google requires the full URL. Will it be possible to update Imperial that it will follow the same logic as before the beta release? Thank you for your support! |
* Adopt VaporTesting * Try fix for #115 * Make the linter happy * Use `pathSegments` also for `authURL` * Update GoogleJWT audience claim to use `accessTokenURL` * Remove redundant test * Update Imperial version in README to `2.0.0-beta.2`
There is an issue with the Google login flow as the completion handler doesn't get called.
The routes seem to be correctly registered, but when I call the routes via postman I get a 404.
I would expect a 400 Bad Request as the route is called without code
The text was updated successfully, but these errors were encountered: