snackdex
02/18/2023, 4:34 PMSessionError: using legacy session, please call the refresh API
when following the authorizer docs https://supertokens.com/docs/thirdparty/serverless/with-aws-lambda/authorizer. This is happening when i call the api from my front end. once this happens then the front end calls the refresh token which returns successful, which then causes the endpoint with the authorizer to get called which results in that error again, which causes the refresh api to get called etc. It basically keeps doing that over and over. Nothing has changed front end wise. Without the authorizer if I do verifySession
in the lambda everything works great.rp_st
02/18/2023, 4:35 PMrp_st
02/18/2023, 4:36 PMsnackdex
02/18/2023, 4:37 PMrp_st
02/18/2023, 4:37 PMrp_st
02/18/2023, 4:37 PMsnackdex
02/18/2023, 4:37 PMrp_st
02/18/2023, 4:38 PMrp_st
02/18/2023, 4:38 PMsnackdex
02/18/2023, 4:38 PMrp_st
02/18/2023, 4:39 PMrp_st
02/18/2023, 4:39 PMsnackdex
02/18/2023, 4:39 PMrp_st
02/18/2023, 4:39 PMsnackdex
02/18/2023, 4:40 PMrp_st
02/18/2023, 4:40 PMsnackdex
02/18/2023, 4:40 PMsnackdex
02/18/2023, 4:41 PMrp_st
02/18/2023, 4:41 PMrp_st
02/18/2023, 4:41 PMsnackdex
02/18/2023, 4:41 PMsnackdex
02/18/2023, 4:49 PMsnackdex
02/18/2023, 4:55 PMst-auth-mode
. This also required me to update supertokens-node in the backend to 13.0.2 for the lambda that handles /auth/* requests. No code change was necessary as supertokens.getAllCORSHeaders()
now includes this as well.