Hello, I am running a setup of nest.js and hasura with supertokens thirdparty-email and sessions, my frontend is react native and we do GraphQL queries to the hasura API with Apollo except for our login that’s just a rest endpoint in our nest.js backend where we use axios. The security is setup so that hasura receives the requests and then it forwards the headers to our who-am-i endpoint that in turn extract the userID from the session with your SessionContainer class after which it refactors the headers into a format that hasura can understand and responds back to hasura with that, hasura in turn uses that for it’s query that then gets sent back to the frontend. 

 All of this has been working as expected in our local development environment, but once we started hosting it things went wrong. I’ve console.logged inside of the login method in the nest.js backend to see that a correct session is returned, which it is, and we’ve used the react-native SDK to see that a session is created which it is as well as console.log() on our app context to see that the session is there as expected. But none the less no headers gets attached to our Apollo requests, does anyone have any idea what could be causing this?

 P.S I’ve also checked the instance of supertokens-core and everything seems to be working as expected there as well. What's really confusing me here is that the frontend seems to have all the data, both in the ctx and when doing checks with your SDK, but it none the less is not used in the apollo requests.

Hi, I have a question, why when I update user metadata by id and user with this id doesn't exist in database, this process create a table entry with this id and data? Can I fix it or check existance of user in easy way?

hi, i have a question. I'm implementing apple thirdparty signin. the flow works fine and apple call my api/auth/callback/apple with response status 200 but the backend don't return to my website domain. In Chrome console i have this error: "Refused to execute inline script because it violates the following Content Security Policy directive: “script-src ‘self’“. Either the ‘unsafe-inline’ keyword, a hash (‘sha256-O+xgXnYzZer/Ev6f0GV4Y96/B1k6naW0deebXvwnaXQ=’), or a nonce (‘nonce-...’) is required to enable inline execution." Can u help me?

Hi, How can i prevent the input field from changing its background on focus? (React) I have set the following styles in ThirdPartyEmailPassword:

inputWrapper: {
  backgroundColor: 'var(--input-background)',
  borderColor: 'var(--input-border)'
},
input: {
  color: 'var(--text-color)',
}

Is it possible to reset a development environment on supertokens cloud?

Is there anywhere where I can access google username after signing up, for example in thirdPartySignInUpPOST?

Can i make sso for 2 domains a.com & b.org with supertokens ?

I tried using supertokens-dotnet in github but got 401 Unauthorized on post to /recipe/session for creating session.

found that need to send apikey in header, fixed

I am trying to use SuperTokens for my website, frontend is React and backend is Python with Connexion/Flask. I just completed the frontend integration without any issues, but the backend integration is not going quite as well. Flask is dependent on werkzeug-2.2.2 but, during install, supertokens-python uninstalls this in favor of werkzeug-2.0.3, which breaks my application.

Installing collected packages: Werkzeug
  Attempting uninstall: Werkzeug
    Found existing installation: Werkzeug 2.2.2
    Uninstalling Werkzeug-2.2.2:
      Successfully uninstalled Werkzeug-2.2.2
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
flask 2.2.2 requires Werkzeug>=2.2.2, but you have werkzeug 2.0.3 which is incompatible.
Successfully installed Werkzeug-2.0.3

EDIT: Recreating my virtual environment and reinstalling all my dependencies seems to have magically solved this issue.

Change email address and pool format?

sso across different domains

I want to use supertokens with AWS API gateway+lambda functions I tried following the recipe https://supertokens.com/docs/emailpassword/serverless/with-aws-lambda/backend-config for the backend config, the tutorial says " Create a config.js file in the root directory of your project. " All I have are bunch of lambda functions called from API gateway. Where do I create these files? 🤔

hey guys

what version of supertokens is compatible with asgiref==3.5?

Are there any best practices documented for doing Liveness probes when running self-hosted SuperTokens within your kubernetes cluster? Right now we do a HTTP call to

/hello

but the probe failes a few times a day with the folloing error:

Liveness probe failed: Get "http://10.244.1.77:3567/hello": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

Hello everyone could you please guide me how I can find all available configuration for Session.init() when I am initializing Session like the following:

supertokens.init({
        framework: "express",
        supertokens: {
            //...
        },
        appInfo: {
            //...
        },
        recipeList: [
            Session.init() // initializes session features
        ]
    });

How safe is it in general to upgrade within the 3.X version range, especially in terms of the PostgreSQL database schema? If the schema would potentially change, would supertokens guarantee that migrations and adjustments are correctly applied upon startup or would it require manual work? And/or would something like this considered a 3.x -> 4.x change?

I'm building a dockerized website with docker-compose. A React frontend and Python Connexion/Flask backend in separate, networked containers. Their container names 'frontend' and 'backend' resolve to their respective IP-addresses within this Docker network. I'm running into a problem while integrating SuperTokens in my backend. I'm setting the

app_info

values to this:

app_info=InputAppInfo(
    app_name="GG-Host",
    api_domain="http://backend:8080",
    website_domain="http://frontend:3000",
    api_base_path="/auth",
    website_base_path="/auth"
)

Running with this configuration causes the following error:

supertokens_python.exceptions.GeneralError: Since your API and website domain are different, for sessions to work, please use https on your apiDomain and don't set cookieSecure to false.

I don't want to use https, since this is all local networking within the Docker network. Changing

api_domain

to use https instead resolves the error, but the sign up form still errors.

Hey, I have a case where a user logs in to supertokens via a browser and its setting the cookies. Then I delete this user from Supertokens, not from the browser. After i delete the user from supertokens calling signout from the browser just return 200 OK but it doesnt remove the cookies from the browser. Im guessing its because the User was deleted but is that an expected behaviour? Any way i can remove the cookies via signout API if the user was deleted?

sign out bug on delete user

I'm running a self-hosted core and just finished setting up my Postgresql. Everything is dockerized and networked with docker-compose. The database and everything else seems to work just fine, however, these errors are logged by the database at startup.

ERROR:  relation "st_key_value" does not exist at character 15
STATEMENT:  SELECT 1 FROM st_key_value LIMIT 1
ERROR:  relation "st_all_auth_recipe_users" does not exist at character 15
STATEMENT:  SELECT 1 FROM st_all_auth_recipe_users LIMIT 1
ERROR:  relation "st_session_access_token_signing_keys" does not exist at character 15
STATEMENT:  SELECT 1 FROM st_session_access_token_signing_keys LIMIT 1
ERROR:  relation "st_session_info" does not exist at character 15
STATEMENT:  SELECT 1 FROM st_session_info LIMIT 1
ERROR:  relation "st_emailpassword_users" does not exist at character 15
STATEMENT:  SELECT 1 FROM st_emailpassword_users LIMIT 1
ERROR:  relation "st_emailpassword_pswd_reset_tokens" does not exist at character 15
STATEMENT:  SELECT 1 FROM st_emailpassword_pswd_reset_tokens LIMIT 1
ERROR:  relation "st_emailverification_verified_emails" does not exist at character 15

It seems SuperToken is trying to access something inside the db which is not there? Though sign up/in works and account are persistent until I rebuild the db container

Hey, i'm getting errors with Facebook login, it worked for me while the app was in development mode on facebook developers, but after moving my app to 'live' on Facebook i'm getting a 400 (corrected from 404) i'm using nest + graphql + react

What should I write in my OpenAPI specification for routes that use SuperTokens

@verify_session()

?

Is there a mechanism for encrypting DB connection string passwords in config.yaml?

Hi, just a question about sessions in react native, should .signout() method delete the session ? Because it is not the case on my implementation and it is a bit of a problem as I am use .doesSessionExist() to determine if the user is signedIn or not

Hey, where can i see what cdi-version I use? Thanks

Hi, any guide on how to use Passwordless and Session management in a plain html, js website with flask backend. Is it even possible right now?

Hi, can we pass additional permissions/scopes while using Social login? for e.g. If someone is signing up with their google account, I can ask them to allow access to google drive too during the process. I am using this for reference -- https://supertokens.com/docs/thirdparty/quick-setup/backend#3-initialise-social-login-providers

Changin oauth scope