https://supertokens.com/ logo
Join Discord
Powered by
hi, anyway i can check old docs of passwordless lo...
# support-questions-legacy
e
hi, anyway i can check old docs of passwordless login we use 
'supertokens-website'
module on the frontend with custom ui, but the docs switched to 
supertokens-web-js
. which is a different implementation?
n
Hi @EdwinN1337, The docs for supertokens-web-js should include the same information (and more on top of that) that the old ones did
Anything specific you were looking for?
Also just to add a little context, supertokens-web-js is the SDK we recommend to use for custom UI. It provides the features that supertokens-website did and adds helper functions for each recipe so you no longer have to call the APIs manually
If you were using supertokens-website with npm, moving to web-js should not be complicated
e
right, well its fague but i got calls from our customer service that users cant login/sessions not being refreshed etc 😉 no error logs whatsoever
so was trying to check docs if i might forget something
i'll move to supertokens-web-js, hope that will sort it out
one of the things we do differently, than other apps (which works), is having a custom domain
cookieDomain
but on the frontend we don't init session, or pass the cookieDomain
which isnt included in supertokens-website, but is in supertokens-web-js
n
Oh it should be included in supertokens-website as well, give me a bit ill pull up the config for it
e
Copy code
js
  supertokens.init({
    cookieDomain: process.env.NODE_ENV === 'production' ? '.lokalist.nl' : undefined,
    ...frontendConfig().appInfo,
  })
ah right we do it sorry
n
Do you know if the refresh API gets called and fails? or if it does not get called at all?
e
is this right?
it fails 401, when entering the website
n
Right there should be more cookies than just that
Can you show me the response headers for the API that is creating a session?
e
we're not logged in right now
so no session is created
https://dashboard.lokalist.nl/ u can check it here (currently working version 2.0, but this is in production)
n
Right so refresh failing on page load is expected behaviour (we call on page load to refresh the session if needed, but since you are logged out it fails)
e
right thats what i thought aswell
once i login
i get these cookies, seems about right aswell
n
Yep seems to be working fine
On your production site, I do see that the 
/code
API is being called but is returning GENERAL_ERROR
/api/auth/signinup/code
This route I mean
Not sure if thats the issue or if its expected behaviour
Oh probably because my email does not exist on your system
e
ah ye, ui is not great hehe
needed to add some feedback there
but the idea was, login once and ur fine 😉 it's only used temporarly for now
if ur not in the system, then u shouldnt be there 😉
n
Ah fair enough :p So I am a little unclear on what the issue is though
e
okey well, i'
n
Do you have any way to recreate it?
e
yeah, well confirmation is that either the users are not opening the link in the correct browser
i don't but thought i was missing something
but this seems to be working fine
(we move to supertokens-web-js, on our new dashboard ;))
thanks anyways!
n
Happy to help, and yep id recommend moving to web-js anyway so that you dont have to keep up with the SDKs logic manually
e
will do!
n
Feel free to ask more questions here if you run into an issue trying to debug this
e
Thanks!
2 Views
PreviousNext
Powered by