Can someone spot what's going wrong here? I had SuperTokens working before but I'm now trying to introduce nginx and it's causing a mess. By default, request URI's are assumed to be refering to static files from my React production build. However, requests to

/api/*

are forwarded to my Python Flask API, which is where the backend SuperTokens SDK is implemented. As mentioned, it worked just before switching to nginx but now all requests to

localhost:80/api/auth

and direct ones to the api

localhost:8080/auth

all return the

404

from this function:

@app.route('/', defaults={'u_path': ''})
@app.route('/<path:u_path>')
def catch_all(u_path: str):
    abort(404)

I am able to reach other API endpoints just fine through for example

http://localhost/api/hello

. nginx

server {
    listen 80;
    root /gg-host/build;
    index index.html;

    location / {
        try_files $uri $uri/ =404;
        add_header Cache-Control "no-cache";
    }

    location /static {
        expires 1y;
        add_header Cache-Control "public";
    }

    location /api {
        include proxy_params;
        proxy_pass http://api:8080;
    }
}

Python Flask app_info

app_info=InputAppInfo(
    app_name="GG-Host",
    api_domain="http://localhost",
    website_domain="http://localhost",
    api_base_path="/api/auth",
    website_base_path="/api/auth"
)

React app_info

appInfo: {
    appName: "GG-Host",
    apiDomain: "http://localhost",
    websiteDomain: "http://localhost",
    apiBasePath: "/api/auth",
    websiteBasePath: "/api/auth"
}

api base path

can anyone help me to setup the quick start with fastapi? im using self hosted with docker, i already try the docs and kinda work, but there's no routes, its like i dont do it here is my code:

python
import uvicorn
 
from fastapi import FastAPI
from fastapi.middleware.cors import CORSMiddleware

# Core Application Instance
app = FastAPI(
    title='Oasys Pipeliner',
    version='v1.0.0',
)

from supertokens_python import init as supertokens_init
from supertokens_python import InputAppInfo, SupertokensConfig
from supertokens_python.recipe import emailpassword, session
from supertokens_python.framework.fastapi import get_middleware
from supertokens_python import get_all_cors_headers

from supertokens_python.recipe import userroles

supertokens_init(
    app_info=InputAppInfo(
        app_name="oasys",
        api_domain="http://localhost:8000",
        website_domain="http://localhost:8000",
        api_base_path="/auth",
        website_base_path="/auth"
    ),
    supertokens_config=SupertokensConfig(
        # try.supertokens.com is for demo purposes. Replace this with the address of your core instance (sign up on supertokens.com), or self host a core.
        connection_uri="http://localhost:3567",
        # api_key="IF YOU HAVE AN API KEY FOR THE CORE, ADD IT HERE"
    ),
    framework='fastapi',
    recipe_list=[
        session.init(), # initializes session features
        emailpassword.init()
    ],
    mode='wsgi' # use wsgi if you are running using gunicorn
)

app.add_middleware(
    CORSMiddleware,
    allow_origins=[
        "http://localhost:8000"
    ],
    allow_credentials=True,
    allow_methods=["GET", "PUT", "POST", "DELETE", "OPTIONS", "PATCH"],
    allow_headers=["Content-Type"] + get_all_cors_headers(),
)

if __name__ == "__main__":
   uvicorn.run("main:app")

Signed up for SaaS dev env. Not receiving the OTPs on phones and emails with the Passwordless logins.

So I'm trying to implement session handling fully, and see the note on the Recipe:

Handling of 401 status code and refreshing the session (steps (4) till (8)) happens automatically via our frontend SDK.

However I don't seem to be getting any automatic retry of the api call from step 7. It technically works by catching a 401 error on the api call itself and using

attemptRefreshingSession()

, but it sounds like that should happen automatically

how do i use the Dashboard.init

and is there an api route for it?

Fastapi setup

Passwordless login email and otp

Automatic refresh

Initialising dashboard

hello every one, since 3 days i'm try to integrate Supertokens to my distributed app(the frontend is with Vuejs and the backend is with flask) i'm starting the whole system with docker-compose en using supertoken Email-Password + Social. it starts without problems, but when the users are redirected after the login process i become an error in the frontend(something went wrong) and an Exception in the backend(supertokens_python.exceptions.GeneralError: No SuperTokens core available to query). please do someone have any idear on how to fix that?

Hi, I have an issue with the combined phone/email field. On some browsers the autocomplete adds an extra space at the end of the email address and then when trying to continue the user gets an error that the email is invalid. Did anyone encounter this issue or has an idea how to resolve it? Thanks

Extra space for email causing validation issues

Hi I want to use react and node and in my application and for authentication authorization purpose supertokens

can any body tell me basic functions in supertokens for react and how to connect it with backend like a functional app authorization and authentication being given by supertokens learning from documentation is bit hard for me first timers

Hey guys, awesome project, love it I 've been debugging this for a few hours. What could be the reason that I don't have

sRefreshToken

cookie. What would be useful information I can provide?

Is it possible to give custom userId to supertokens.? I know supertokens uses uuid. I was taking a look at the override functions. Wondering if I can pregenerate the user_id that will be used in supertokens table

Hey guys. I also wanna express how happy I'm with your project. It was exactly what we we're looking for and are so happy we found it. I have the following two questions:

1.) Do you have an updated status or a rough timeline on the 2FA TOPT feature? We're asking because this feature would be super important for us in the long run. So we don't care if takes a week, a month or quarter. But we just want to make sure, that in half a year or so, we can support it without needing to switch auth service

2.) The second question is a bit more complex. And its concerning your Go-Fiber example implementation in your go sdk. These lines here: https://github.com/supertokens/supertokens-golang/blob/master/examples/with-fiber/main.go#L119-L137 show that you are using the NewFastHTTPHandler function from fastHTTP that says in its documentation: "NewFastHTTPHandler wraps net/http handler to fasthttp request handler, so it can be passed to fasthttp server. While this function may be used for easy switching from net/http to fasthttp, it has the following drawbacks comparing to using manually written fasthttp: missing fasthttp functionatlity and slower speed. Now the question, it shouldn't be to hard to directly have a version of your session.VerifySession middleware that can handle a fasthttp request. I've looked through the implementation and only a few minor details would be needed to change. I'm just hesitating on how to best implement it: Either as PR directly to your GO SDK 2.) or some how write my own verifySession handler outside your library which looks really hard, because some internal classes are not exported which I would need. Any ideas on how to go about this, without directly forking your go sdk and using the then modified sdk in my projects?

User ID mapping

TOTP

Modification to verifySession

Hello, Could you please guide me about this question: https://stackoverflow.com/questions/73775773/how-to-use-supertokens-refreshsession

Hey! Sure. I'll answer on SO

answered!

Hi, I am using this example for third-party social login https://github.com/supertokens/supertokens-auth-react/tree/master/examples/with-thirdparty I replaced (core's URL)

connectionURI: "https://try.supertokens.com",

with

connectionURI: "http://localhost:8080",

in

api-server.js

After clicking "**continue with google**", I got redirected to "supertokens.com", then to the google login screen. I don't see any logs in

core

service after initiating the login flow. Is it still sending request to try.supertokens.com somewhere? Why is it redirecting to supertokens.com? Is it hard-coded somewhere?

is there any

onUserCreated

function? basically like a hook, when a user created, do something I know it's possible to do in

consumeCode

,

thirdPartySignInUp

. Just wondering if there's a cleaner way to do this

Login with google issue