We will not allow changing of the path, but we currently allow adding a prefix (via

apiBasePath

config) to the path. You can do the following: - Override the signout API on the backend to have the logic of your /logout API. OR; - Use the

preAPIHook

config to change the path where the request is going.

was looking for the docs, I see, so we just return a modified URL here if action is

SIGN_OUT

correct?

Yes. Corrrect.

Also, can I see the sign out API call response? Your cookies r not being cleared.. so need to debug that

Most likely cause of a configuration issue

slr, about that, the default implementation for

signout

in the backend has been disabled so we think that's contributing to the issue

Ahh I see.

so when the frontend calls the

/signout

endpoint, it gets a 404, thus the cookie remained 🤷‍♂️

Fair enough.

But then it shouldn’t have changed IRTFrontend to remove

So that’s odd

but we'll try to ride in preapi hook, I think it should solve the issue and the cookies should get cleared

Alright!

I'm not working on it directly but I'll let you know the outcome when my teammate gets back on me xD

he was playing on enabling/disabling the signout implementation on the backend as well so the state probably got mixed in the process 🤷‍♂️

@User , we have added an example of how you can use the override feature to make use of localstorage instead of cookies for session management: https://supertokens.io/recipe-redirect?to=/advanced-customizations/examples/localstorage/about

if we

signOut()

then login again, the behavior of the

sIRTFrontend

cookie doesn't seem right. to reproduce: 1. Login 2. Signout 3. Login again from what we've observed, when

1

happens, the

sIRTFrontend

cookie gets set. Upon doing

2

the cookie gets set to

remove

. However when doing

3

, the

sIRTFrontend

value remains as

remove

then when performing

isAuthenticated()

, it always returns

false

because `sIRTFrontend`'s value is

remove

even though we have the access and refresh token cookies from the successful login. Seems like the culprit is here: https://github.com/supertokens/supertokens-website/blob/85e9f69bb7a17b6f807e5a1e457fc9163463a6e3/lib/ts/fetch.ts#L599 when the session has been created, I think

sIRTFrontend

should be set again. That, or remove that cookie as well during

signOut()

🤷‍♂️ we're currently getting away with the issue by doing the latter, which is to remove the

sIRTFrontend

cookie manually as well after

signOut()

. are we doing something wrong somehow?

Can I see your backend and frontend config? Cause the behaviour you mentioned should not be happening. For example, visit emailpassword.demo.supertokens.io and see how it should be behaving.

backend

What’s the appInfo?

Can u DM me the values of the websiteDomain and apiDomain?

nah I think I can share here just fine, we're still on development

Alright. And you are accessing the site on http://localhost as well?

yes

Or some port number?

on a different port number

vue app on port 8081, api on 8080

You should add the port number to the apiDomain and websiteDomain values

So websiteDomain should be http://localhost:8081

And apiDomain should be http://localhost:8080