Channels
#support-questions
- f
frederic
07/22/2021, 5:08 PMshould I be doing it differently - f
frederic
07/22/2021, 5:09 PMwithout the return block I have no errors - r
rp
07/22/2021, 5:15 PMyour file needs to be.tsx - r
rp
07/22/2021, 5:15 PM@User ^ - m
mantis
07/22/2021, 6:37 PM@User I fixed the problem. On the supertokens-node init I set
tocookieSameSite
."none" - m
mantis
07/22/2021, 6:38 PMThis fixes the deprecation message in Firefox 90. - r
rp
07/22/2021, 6:44 PMCool! - f
frederic
07/23/2021, 8:08 AMyes that sorted out the problem. Might be worth adding a note to the https://supertokens.io/docs/thirdpartyemailpassword/advanced-customizations/react-component-override/usage section to let users know they will need to change the supertokensConfig file extension from js/ts to jsx/tsx before updating the recipe. Also needed to use /** @jsxImportSource @emotion/react / instead of /* @jsx jsx */ in my case. - f
frederic
07/23/2021, 8:08 AMThanks for the help @User - r
rp
07/23/2021, 10:41 AM@User sounds good. Will incorporate those in the docs soon. - l
lomz
07/23/2021, 8:54 PMSweet project 🙂 I'm currently evaluating identity providers for my company. From my due diligence, I got the impression that SSO was implemented but optional in supertokens... but it shows SSO on the roadmap. What is the status of SSO? - r
rp
07/24/2021, 4:09 AMHey @lomz. When you say SSO, do you mean integration with SAML or Open ID connect providers? Or do you mean you want to allow a user to log onto multiple apps (on different domains) via a single login page? - u
user
07/24/2021, 11:46 AMhi, can't we use
? I am gettingwebsiteDomain: "http://localhost:4000"
fromError: Please provide a valid domain namenormaliseURLDomainOrThrowError - u
user
07/24/2021, 11:46 AMjust wanted to test it locally, not sure if I'm doing something wrong - r
rp
07/24/2021, 11:46 AMwhat version of the sdk are you using? - u
user
07/24/2021, 11:47 AM"supertokens-node": "^6.0.3" - r
rp
07/24/2021, 11:47 AMcan you show your whole config object? - r
rp
07/24/2021, 11:47 AMi mean the init object - u
user
07/24/2021, 11:47 AMCopy codejavascript supertokens.init({ supertokens: { connectionURI: "http://localhost:3567", }, appInfo: { appName: "appname", websiteDomain: "http://localhost:4000", // FIXME this should go into the environment configs apiDomain: "/api/", }, recipeList: [Session.init(), EmailPassword.init()], }); - r
rp
07/24/2021, 11:48 AMthe
should beapiDomain
as well.http://localhost:4000 - r
rp
07/24/2021, 11:48 AMyou should set the
to beapiBasePath/api/ - r
rp
07/24/2021, 11:48 AMand the same goes for the frontend. - u
user
07/24/2021, 11:49 AMah my bad - u
user
07/24/2021, 11:49 AMI misread the appinfo documentation - r
rp
07/24/2021, 11:50 AMno worries 🙂 - u
user
07/24/2021, 11:51 AMmixed the domain and base path 😫 - u
user
07/24/2021, 11:51 AMthanks for quick response - r
rp
07/24/2021, 11:51 AMfair enough.. maybe we should have better error messages.. hehe - b
B0BAI
07/24/2021, 12:44 PMHey what does "Handshake for session" mean? - r
rp
07/24/2021, 12:48 PMIt's used to fetch session info like the public signing key. So that the backend SDK can do session verification without calling the core.