Closed printMalik closed 1 year ago
sAccessToken=eyJraWQiOiJkLTE2OTEwMjA3MjgxOTMiLCJ0eXAiOiJKV1QiLCJ2ZXJzaW9uIjoiMyIsImFsZyI6IlJTMjU2In0.eyJpYXQiOjEuNjkxNjIzMDQ2RTksImV4cCI6MS42OTE2MjY2NDZFOSwiYW50aUNzcmZUb2tlbiI6bnVsbCwic3ViIjoiMGI5NzY2YmEtZjkxMy00M2ZmLWIyOGItZDU1ZTkwNjUwNWI1IiwiSW5fR2FtZSI6eyJSb2xlIjoiR00iLCJHYW1lIjoiMSIsIlBhcnR5IjoiTm9uZSJ9LCJpc3MiOiJodHRwOi8vbG9jYWxob3N0OjgwMDEvYXV0aCIsInNlc3Npb25IYW5kbGUiOiI1MjlmMTEzMC1kMjhlLTQxY2QtODBiNC1kNWVhMTZiYWMzOWEiLCJwYXJlbnRSZWZyZXNoVG9rZW5IYXNoMSI6IjE4MjI1MjJjZGNlNTc1YjlmMjJiYzM2YjkyNzNhZjkwZmMyZjFjNjBmNWI1OGYyNjM3NTk4ZjBkYThhMDc3MmMiLCJlbWFpbCI6ImV4cGxvaXRlckBiYXIuY29tIiwicmVmcmVzaFRva2VuSGFzaDEiOiI4NDBiOGFmNmU2MjFmMWU4MDFkNGEzODkzYzliZDQ1ZTY4NWRlYTA4N2Q2MDEzMTYzYjliMWUzMjNjNmNmNDExIiwidXNlcm5hbWUiOiJleHBsb2l0QWNjb3VudCJ9.WFs0XgzwnR065Xh-GEXMbC9f44zCVjtHtpUsOK1xGAVHCQ5UuHGtUZBOJAyHLVMvg_4wjRe_hzJLQugOxlGctAK4ZO_yFFcpIPekl2kvqihvbXAKwMp9UXLd5CqqgkJkeAlRh66BXWk2EjHEZ4LmMS3aK7di9h1SpikNrEeQyWzwSTdnQKYaI0czsh2XVyd8nO9n3RK8I_IdPpsHmjY0y3-bKD_ahre_Y6IHP8zj6RZb9GHpR0-u0O14Ex_Uwuszc2rtjoAzqHUbm8pfYdrRNuwCmqKoudXeRPRChCZTARoRCoEu_5LfpkeDnRuLo76Z9Uarvgf-ZBAd1qZ93Y_KDA
This issue has been fixed. There was a bug in the supertokens core which has now been fixed in core version >= 6.0.10
Managed core v5 Frontend: supertokens-auth-react 0.31.5 Backend: supertokens-python 0.13
Description
session: SessionContainer = Depends(verify_session())
Backend debug logs when calling signOut & token used in the request sAccessToken=
ST configs
Here are the frontend and backend configs. We aren't using the third party providers yet so we have them commented out. I have removed them for this post to reduce clutter