Hello, I have been having trouble with getting Next.JS App Directory SSR to work properly. I've been following the documentation on https://supertokens.com/docs/thirdparty/nextjs/app-directory/protecting-route#sessions-with-server-components--pre and looked at the repository (https://github.com/supertokens/next.js/tree/canary/examples/with-supertokens/app). (I last checked these pages and followed them today, 2/9/2024) The components sessionAuthForNextJS.tsx and tryRefreshClientComponent.tsx are the same and I followed the code stated in home.tsx. Looking at my configuration files, they seem to be correct. When I attempt to log in, it works just fine and such. Then if I try to go to my dashboard, which has the SSR authentication requirement, I will first be redirected to the auth page for a moment then pushed to the home page '/'. Then every other attempt of trying to go to the dashboard will just continue to redirect me to the home page '/'. If convert the SSR pages into their client side version then it works just fine, however I want to use SSR for increased performance and user experience. I then got confused with the middleware, thinking it was part of the SSR before realizing it was only for APIs, but the middleware approach did fix my issues, until expiration occurred and I'd get a "Authentication required" message. As a temporary fix to this, the user would need to go back to the home page and then they'd be able to go to the dashboard and its sub pages. This sort of works but there are pages where users would go straight to a sub page within the dashboard, so they'd get this message often. Figuring out that the middleware was only for APIs, I went back and commented it out. I am now at square one with SSR authentication again and can't seem to figure out why I am only redirected to the home page and never allowed into my dashboard.

Is there an easy way to add claims (like the users email) to the session on the frontend? Asking because im following the flow for OIDC login with Okta with a custom built UI and we have to call signInAndUp() from the frontend like here https://supertokens.com/docs/thirdparty/custom-ui/thirdparty-login. We get the users email from the signInAndUp response but not sure where we can add it to the session from here. Unless maybe added a custom next api route to invoke the createNewSession function from supertokens-node?

Hi , I'm trying to implement supertoken request call in ionic angular, For get api it is fine but for post , our backend server is returning 440 "try refresh token" Implementation on ionic app FE : `SuperTokensRequest.init({ refreshTokenUrl:

${baseUrl}/session/refresh

, sessionExpiredStatusCode: 440, viaInterceptor: false, });`

await SuperTokensRequest.post(
      url,
      fetchConfig
    );

Hi, we're using supertokens-node on our backend and i've been trying to figure out how to access the

last_active

info for a user. I can see there's a table for it but I can't seem to see how I can retrieve that data using the SDK. I wanted to avoid directly querying the table because it makes testing easier but is this possible at all?

I tried to run the vue router example in the docs, but I couldn't get it to work with:

path: "/auth*",

. By reading https://router.vuejs.org/guide/migration/#Removed-star-or-catch-all-routes, it seems that catch-all routes handling changed. I managed to get it to work with

path: "/auth:pathMatch(.*)*"

. Is this the correct way to do it?

Hi there! I am trying to create a dashboard user like this

curl --location --request POST 'http://localhost:3567/api/recipe/dashboard/user' \
--header 'rid: dashboard' \
--header 'Content-Type: application/json' \
--data-raw '{"email":"akrem@agenta.com" ,"password": "pass"}'

however am getting this error and I don't find docs about it

AppId or tenantId not found => Tenant with the following connectionURIDomain, appId and tenantId combination not found: (, public, api)

Hello guy ! Small question for you, we are using the supertokens-web-js library and I noticed that when we call the

createCode

function it's seems to also call the

session/refresh

do you know why ? Many thanks.

self-hosted supertokens core 6.0 on GCP Cloud Run, getting error "Invalid API Key" when trying to access the

/hello

path, but when I switch back to 5.0 with the same environment variables, it runs without issue. I'm using the same environment variables in both. Not a big issue for me because I can use 5.0, just thought I should let you guys know, maybe I'm missing something.

I believe the answer is no, but I wanted to check: can SuperTokens act as the SAML service provider? I need to provide an application that can communicate with auth services for a university, and universities overwhelmingly use Shibboleth SAML. Is there a way to use SuperTokens in my app currently?

@rp_st any ETA on 2FA support?