You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this repo, I'm creating an auth flow that should (I think) work for Google OIDC. The deployed SST app works as expected, but the sst dev behavior differs in unexpected ways.
Expected result: A 200 response, with a JSON body detailing a 302 redirect
Observed result: A 200 response, but no response body
The CloudWatch logs (see the sanitized logs in cloudwatch_logs.txt) show that when running sst dev and hitting the endpoint, the auth handler Lambda function is receiving the correct message (the JSON body with the 302 info).
We can actually view the expected result if we sst deploy instead of sst dev
The text was updated successfully, but these errors were encountered:
madisonbullard
changed the title
Behavior differs between sst dev and sst deploy (Ion auth handler)
Behavior differs between sst dev and sst deploy (Ion auth handler using GoogleAdapter)
Jun 13, 2024
I can't get a response body from an auth handler Function when running
sst dev
, but it behaves as expected aftersst deploy
.I created a repo to demonstrate this issue: https://github.com/madisonbullard/sst-ion-auth-issue
Details included in the README, referenced here:
The text was updated successfully, but these errors were encountered: