Hello, We have are starting to have user unable to reset their passwords. We are using the "invite flow" describe here: https://supertokens.com/docs/thirdpartyemailpassword/common-customizations/disable-sign-up/emailpassword-changes On the screen you can see the password reset page, it is in french but the text doesn't really matter is classic form reset text translated. The red text just informs the user that there was an error. When looking in the network tab of the dev console, we can see that the endpoint called by supertoken is incorrect and different from what it should be. Endpoint called by supertoken with that specific user:

/auth/Public%3E/user/password/reset

What is expected (and hat we are calling when we try to reproduce ) :

/auth/user/passwordreset/

Any idea where this is coming from ?

https://supertokens.com/docs/thirdpartyemailpassword/common-customizations/sessions/handling-session-expiry Can I use this handler with Next.js 13/14?

What field in the session token payload is the email verification recipe checking? I want to make sure it's properly set. Also want to get it from the SSO.

Hey all, is there a recommended process for debugging "Something went wrong. Please try again." on the login screen? Been getting this one recently - can't see what code change might have caused it. No error or logs in either client or server console. Network tab shows one successful request to "api/auth/authorisationalurl" and nothing else UPDATE: It was a compatibility issue somewhere between

supertokens-auth-react

,

supertokens-node

and

supertokens-web-js

. This is not the first time I've been stung and I'm wondering what might be involved in a more usable compatibility table - I'd be open to building an open source compatibility calculator if there is a need for it

Hi everyone, I am using managed supertoken core, with email password recipe for React Frontend client side, everything is working fine, but my access token is not getting refreshed with refresh token, once expired.

We have used thirdpartyemailpassword and email verification recipes together, the users can either login with email password or third party probiders such as Google, Azure, okta, etc. Is there any way to find which login method the user logged in with?

Hi, is it possible to get email from the session like user_id? session: SessionContainer = request.supertokens user_id = session.get_user_id() email = session.get_email()

Hi there. Thank you to all the developers /maintainers of supertokens! I've been loving the development experience so far. I have been having a weird issue I was hoping I could get some help with. On initial login locally I am always getting a refresh token through the third party login flow (right now I am using google). When i deployed my app to AWS, I now only get a refresh token on the initial login flow, but not on subsequent logins. I would guess this is something on the google side, but I was wondering if this is something others have experiences or have some familiarity with.

it is possible with the frontend SDK (the web-js one) to fetch user metadata?

Hi all, I've noticed that the response times for our python server endpoints using supertokens sessions were longer than expected. So I timed each part of our verify middleware and saw that

verify_session()

was taking around 200~300ms, taking up a majority of the response time. Is this normal? How long is

verify_session()

usually expected to take? I would like to know if there are ways to get this time way down. Here's the snippet:

start = time.time() * 1000
session_recipe = SessionRecipe.get_instance()
supertokens_session = await session_recipe.verify_session(
    request=base_req,
    anti_csrf_check=True,
    session_required=True,
    check_database=False,
    override_global_claim_validators=None,
    user_context=None,
)
end = time.time() * 1000