Mr. Lurs05/21/2022, 6:23 PM
rp05/21/2022, 6:24 PM
Mr. Lurs05/21/2022, 6:31 PM
rp05/21/2022, 6:32 PM
Mr. Lurs05/21/2022, 6:34 PM
martin805/22/2022, 2:09 AM
make sure to change that to wherever your supertokens API is, we have that set in our Angular environment file. You will also see cookieService being used in the super-tokens service. It's this npm package; https://www.npmjs.com/package/ngx-cookie-service; make sure to add it to your module.
cookie, when implementing we found that without deleting this, a user would not be signed out properly. Is there a function within Supertokens that handles this without us having to do it manually? I do recall when implementing, when calling the browser sdk sign out function, ‘sIRTFrontend’ cookie would be left as residue. Everything else seemed to work, manually removing this cookie looks like it does the trick. Is there anything should be done differently?
rp05/22/2022, 5:07 AM
, we set it to
if the user is not logged in because Safari clears frontend set cookies after 7 days of inactivity, due to which the frontend could not reliably determine if a user is logged in - since if it's missing, then we don't know if Safari cleared it or if the user actually logged out. So on logout, we set it to
which means that the user is indeed logged out. If it's missing, then we query the refresh API, which would fail (if the user is logged out), and then we set it to
martin805/22/2022, 5:57 AM
rather than literally deleting the cookie?
rp05/22/2022, 5:59 AM