Hello everyone can some share some repo showing implementation of supertoken with python django for social login without password using plain javascript in front end

Hey all, is there a way with Supertokens to handle account management ? I have multiple users with different roles (admin, user) linked to one account. These users can only retrieve data from entries linked to that account. Pretty common for B2B apps. How do you deal with that ? Thanks a lot

need help about flask API

Colleagues, I need some advice. Can I use Google OAuth Access Token to authorize my server? How do I validate them?

hey :). we are having an issue with the redirect uri returned for Apple on the web. the code that creates the redirect uri uses the API base path instead of the UI base path.

I just setup Supertokens and got it linked with my db and I got the init command added to my api. Do I have to create all the routes for my API or is there something i'm missing?

Can I share tokens somehow between subdomains? So let's say I have app.todolists.io and admin.todolists.io so I can do some user management or whatever in the adminpanel. Can I share my login between those two apps so I don't have to reauthenticate? (and maybe I would have an account.todolists.io for language and theme preference for example, or to enable 2fa in the future ;-))

hi, i faced an issue.

Error: SuperTokens core threw an error for a POST request to path: '/recipe/accountlinking/user/primary' with status code: 402 and message: Account linking feature is not enabled for this app. Please contact support to enable it.

hi @rp_st I test endpoints via postman. For this, I need to refresh tokens at regular intervals. Is there a token for postman that does not require refresh?

Hi Supertokens Team, I hope this message finds you well. I am currently working on integrating Supertokens into my application, which consists of Vue.js on the frontend and Nest.js on the backend. Initially, I successfully implemented the Supertokens login functionality using the SaaS version, and everything worked smoothly. To facilitate local development, I decided to switch to the Docker version of Supertokens by setting up a local instance and updating the connectionUrl accordingly. After successfully completing the setup, including table creation, both the Supertokens core and database containers appear to be running correctly on my local environment. However, upon switching the backend's connectionUri to the local URL, I encountered an issue. The login form displays as expected, and I can successfully log in with Google authentication. However, instead of being redirected to the application's homepage, the Supertokens session refresh logs continuously appear, causing an infinite loop. When I revert the connectionUri to the SaaS version, everything functions correctly. I've attached a portion of the logs generated endlessly on the frontend for your reference. Could you please provide guidance on what might be causing this issue? Any insights or suggestions would be greatly appreciated.