Setting up multiple frontends for one backend for ...
# support-questions-legacy
t
Setting up multiple frontends for one backend for python flask , what value of website domain to keep if we have multiple frontend consuming the same backend , will the origin thing work for python flask as well as mentioned in the docs @rp_st
r
Hey. If you wait a week, we will be releasing this feature in python.
t
Noted thanks . Is there any other way to test it for python meanwhile , I just want to test the flow
r
There is. It’s a little complex and really depends on your use case
What’s the use case?
t
So the use case is that I have 2 frontend apps which need the same authentication which is why we intend to have a single backend auth . Both the apps are on different domains Also the use case is that if a user logs in one of the apps and goes to the other app he is automatically logged in
r
Right. And the two domains are sub domains? Or totally different base domains?
t
Use case 1 : For sub domains with same base domain Use case 2 : For different base domains I have both the use cases so would want to understand for both
r
for use case 1, you can have a common login page and then use session sharing across sub domains: https://supertokens.com/docs/session/common-customizations/sessions/share-sessions-across-sub-domains
for use case 2, it will require us to be an oauth provider, which we are working on. But until then, you can basically create a domain that has supertokens integrated in it, and when the user logs in, send the access token to the client app in a query param, and then use that access token there to create a new session on the client app.
3 Views