Disable sign up

It seems like the post-login token ingestion / confirmation isn't working, I'm presuming its because we're using HashRouter (routes are /#/foo). Has anyone had this problem?

I'm wrapping my NextJS app with

ThirdPartyEmailPasswordAuth

from

supertokens-auth-react

to expose the Supertokens context to the any of the components. When I disable all cookies in my browser the

ThirdPartyEmailPasswordAuth

causes it to fail because there is no localStorage or cookies. Is there a preferred way to gracefully handle the

ThirdPartyEmailPasswordAuth

if cookies are disabled?

Hi there! Is it possible to restart / clean up the dev env ?

We messed up with some tables and its probably causing the problems we are getting of CORS

We are getting "internal error" from Supertokens Core

Cookies being disabled

Restart dev env in SaaS

@Alankazam see this: https://discord.com/channels/603466164219281420/996172499584823438/996253495894216754

@rp how can i use custom id for user ids

Is it possible to verify a session, from a different backend by initializing the same core?

Custom ID

Verifying a session from a different backend

After fixing the cors issue, now the session doesnt last for long (maybe 30 minutes) on the second front-end. Its as if the access token doesnt refresh automatically. Anything special I need to do?

Hey @rp does Supertokens support Saml using BoxyHq with passwordless recipe?

Also, any estimates on SSO?

SAML with passwordless

SSO (us being an OAuth provider) should be available in 2-3 months

Hey guys, I am using

supertokens-python==0.8.2

with

Django==4.0.6

and resend code is not working for passwordless. Is it a known issue for python SDK version I am using? It is a POST request from frontend to the URL

signinup/code/resend

with

preAuthSessionId

and

deviceId

payload. The response says

"status": "OK"

with 200 status, and the code is not being delivered. I cannot see any logs on the backend that indicate code resend attempt.

SSO us being an OAuth provider should be

hey, we're trying to add apple as a third party provider (since apple don't allow social login if you don't have apple as option) when we add apple as provider we get the famous

[object Object]

error, can't figure out why

I want to make that users logged on the main domain to be logged in on the subdomains as well with the same account and how do I install supertokens on there?

Also I'm using Hostinger

can we have non-minified version of web-js sdk in the bundle on jsdeliver, it will be easier to debug. currently it is minified

No minified version of web js

Hey there, is there a way to let supertokens use int / bigint instead of uuid as the primary key for the email_passwords table (and probably all other)? Like

user_id

would be 1 instead of "uq814uq-81412...."

👋🏼 Does super tokens support B2B easily similar to Auth0?

Hey all, Any idea how to implement SuperTokens with Chrome extensions? I am stuck trying to get it to work.

Does

supertokens-web

attempt a refresh on all 401s by default, or only when other response headers are also found (e.g.

rid

)? I saw my front-end looping requests when my API sent back an explicit 401 (not from

supertokens-node

, but from my own controller). It's fixed if I set the

sessionExpiredStatusCode

, but I thought there would be some other logic besides attempting a refresh on all 401s. Is this intended? I'm on

"supertokens-website": "^10.1.0",

and

"supertokens-node": "^9.2.3"

Infinite loop 401