Hi, I'm facing a problem with the

st-auth-mode

request header. First, I do a signup request (using the email password recipe) where I set the header

st-auth-mode: cookie

. I then get a response with

Set-Cookie

headers for the access token and refresh token. This is as expected. Next, I do a signup request where I don't set the

st-auth-mode

header. I then get a response with both

Set-Cookie

headers and

st-access-token

and

st-refresh-token

headers. I do not expect to get the

Set-Cookie

headers. I do a signup request one more time, again without setting the

st-auth-mode

header. This time only the

st-access-token

and

st-refresh-token

headers are set. This is as expected. All signup requests I do afterwards without the

st-access-token

header give the same proper result. The second request should not have returned the

Set-Cookie

headers. Is this a known issue or am I doing something wrong?

Hello, I am having issue with API /signinup, it is being called twice, already looked at other discussions in here but I still don't know how to prevent I am using SuperTokens Core (Managed) v7.0, front-end I am using React with "supertokens-auth-react": "0.31.5", back-end is ExpressJS with "supertokens-node": "13.6.0"

Hi, I'm using multi tenants and wanted to share the session accros sub domains. So i referred here; https://supertokens.com/docs/emailpassword/common-customizations/sessions/share-sessions-across-sub-domains But the example there uses the prebuilt UI (

supertokens-auth-react

), and i'm using my custom UI (

supertokens-web-js

) How can i accomplish sharing session across domains with the custom UI? Thank you

Is there a simple way of retrieving a user email once they've signed in in the same way you retrieve userId with

await Session.getUserId()

? I couldn't see how to do it from the Get User Info documentation: https://supertokens.com/docs/thirdpartyemailpassword/common-customizations/get-user-info

I'm using the nextjs started integration and when I have an active user session and I hit the /auth route I get caught in an endless redirect loop. Everything's been followed exactly as the integration says

Hello. If I create a instance of axios, supertoken is not detecting session cookies. I am using supertokens-web-js in nuxt.js 2 // Here is my code plugins/axios-cache-setup.js

import axios from 'axios'
import { setupCache } from 'axios-cache-interceptor/dev'

export default function ({ $config }, inject) {
  // Create axios instance
  const axiosInstance = axios.create({
    baseURL: $config.baseURL, 
  })
   // Set up caching
  // Set axios instance to Nuxt context
  const axiosWithCache = setupCache(axiosInstance, {
    methods: ['get', 'post'],
    debug: console.log,
  })

  inject('axiosCache', axiosWithCache)
}

Hi, I was wondering how to create a custom signin/signup UI for a NextJS integration. I am currently successfully using the pre build UI [1], however I'm not sure how to start creating a custom UI. - Should it be in the same file (

pages/auth/[[...path]].tsx

)? If so, where do I put my components? If not, which file should I use? - The example of the custom email password signin [2] only shows the callback function. Is there an example of building a custom UI in NextJS? - Is there a certain structure to keep in mind such that I can easily later add alternative signin/signup methods? [1]: https://supertokens.com/docs/emailpassword/nextjs/setting-up-frontend [2]: https://supertokens.com/docs/emailpassword/custom-ui/email-password-login

Hi, I would appreciate some help with getting session authorization to work with a second api. I have NextJS 14 setup with app router and a backend api with Express. Server sided components are getting 'unauthorised' responses from the Express api.

I have supertokens core behind nginx reverse proxy. I'm forwarding these headers: proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; I get "hello" only if i remove the Host header. So I'm wondering how to bind the core instance with the A/AAAA assigned record. In the attached docs I found SUPERTOKENS_HOST but it doesnt seem to have effect on the reverse proxy, still getting HTTP Status 400 – Bad Request when forwarding the host. this is my config.yaml core_config_version: 0 host: "0.0.0.0" supertokens_host: "https://supertokens.example.com"

Hey, I've this error Please advise Using Flask, with SQLAlchemy

/usr/local/lib/python3.9/site-packages/sqlalchemy/orm/context.py:2695: RuntimeWarning: coroutine 'Supertokens.middleware' was never awaited
  _instance = loading._instance_processor(
RuntimeWarning: Enable tracemalloc to get the object allocation traceback

ERROR:APP_NAME:Exception on /case/ [GET]
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/flask/app.py", line 2190, in wsgi_app
    response = self.full_dispatch_request()
  File "/usr/local/lib/python3.9/site-packages/flask/app.py", line 1486, in full_dispatch_request
    rv = self.handle_user_exception(e)
  File "/usr/local/lib/python3.9/site-packages/flask_cors/extension.py", line 176, in wrapped_function
    return cors_after_request(app.make_response(f(*args, **kwargs)))
  File "/usr/local/lib/python3.9/site-packages/flask/app.py", line 1482, in full_dispatch_request
    rv = self.preprocess_request()
  File "/usr/local/lib/python3.9/site-packages/flask/app.py", line 1974, in preprocess_request
    rv = self.ensure_sync(before_func)()
  File "/usr/local/lib/python3.9/site-packages/supertokens_python/framework/flask/flask_middleware.py", line 54, in _
    result: Union[BaseResponse, None] = sync(st.middleware(request_, response_))
  File "/usr/local/lib/python3.9/site-packages/supertokens_python/async_to_sync_wrapper.py", line 33, in sync
    return loop.run_until_complete(co)
  File "/usr/local/lib/python3.9/asyncio/base_events.py", line 623, in run_until_complete
    self._check_running()
  File "/usr/local/lib/python3.9/asyncio/base_events.py", line 583, in _check_running
    raise RuntimeError('This event loop is already running')
RuntimeError: This event loop is already running