https://supertokens.com/
Join Discord
Think I might have a bug report regarding user meta/the dashboard. I'm using ThirdPartyEmailPasswo...
o

oldhack1364

about 3 years ago
Think I might have a bug report regarding user meta/the dashboard. I'm using ThirdPartyEmailPassword receipie in my FE and BE configs. And UserMeta/Dashboard in my BE config When I go to the dashboard to edit a users name and click save I get these logs:
Error: Initialisation not done. Did you forget to call the SuperTokens.init function?
at Function.getInstanceOrThrowError (/app/node_modules/supertokens-node/lib/build/recipe/emailpassword/recipe.js:199:15)
at /app/node_modules/supertokens-node/lib/build/recipe/dashboard/api/userdetails/userPut.js:76:18
at Generator.next (<anonymous>)
at /app/node_modules/supertokens-node/lib/build/recipe/dashboard/api/userdetails/userPut.js:30:75
at new Promise (<anonymous>)
But when I refresh the dashboard, the meta has actually saved
o
r
n
  • 3
  • 21
  • 58
Hi I've got a problem with Angular + Capacitor + Supertokens. In the web version everything works pe...
m

mnky_js

over 1 year ago
Hi I've got a problem with Angular + Capacitor + Supertokens. In the web version everything works perfectly but when I test the app in iOS for example, then after the login the refresh call of doom is starting 😄
m
r
r
  • 3
  • 32
  • 57
<@498057949541826571> need support, when we deploy Supertoken core to decrease access token validity...
u

[CATs] ya ong | [GUnS] bakins

over 1 year ago
@rp_st need support, when we deploy Supertoken core to decrease access token validity from 30 days to one hour, we've got this error:
jwt invalid: failed to deserialize token claims: could not get token claims: go-jose/go-jose: unsupported key type/format
that's happen when and after we deploy it. Any reason why?
u
r
  • 2
  • 9
  • 57
Hey all. My company is looking to transition over to SuperTokens. After looking at some things we se...
e

EJ

over 2 years ago
Hey all. My company is looking to transition over to SuperTokens. After looking at some things we see that our current auth solution uses PKCE, but it appears that SuperTokens does not support OAuth 2.0 flows, but that does not seem quite right to me. Would someone be able to point me towards the proper documentation to answer this question?
e
r
e
  • 3
  • 22
  • 57
Hi, Can I use SuperTokens with Traefik ForwardAuth?
h

hamade

over 2 years ago
Hi, Can I use SuperTokens with Traefik ForwardAuth?
h
r
  • 2
  • 7
  • 57
Hi, I'm looking for some clarification on the pricing change that seemed to happen March 18th. Is mu...
b

Bailey

over 1 year ago
Hi, I'm looking for some clarification on the pricing change that seemed to happen March 18th. Is multi-factor authentication support via SMS something that we will be charged for even if we aren't using SuperToken's sending services? We're using our own service to send the text message after overriding the
smsDelivery
function, under the
Passwordless
recipe, and we were not expecting the new $100/month price minimum.
b
r
  • 2
  • 8
  • 56
Hi, I am stuggling to find how to refresh the session using the header transfer method , by manual...
l

luiss

almost 2 years ago
Hi, I am stuggling to find how to refresh the session using the header transfer method , by manually doing XHR Requests to the /auth/ endpoints. It seems the that refreshed token is sent using cookies instead of response headers. Currently I am trying with the following POST: What am I doing wrong?
api.post('/auth/session/refresh', 
           null,
           {
             headers: {
               Rid: "session",
               Authorization: "Bearer "+ refreshToken,
               "St-Auth-mode": "header", 
            }
          });
l
r
  • 2
  • 3
  • 56
KeyError 'access_token' when fetching profile info via Google
j

jaynil_71939

about 2 years ago
Hi Team, We are getting a KeyError 'access_token' on our Flask backend when fetching profile info via Google: supertokens_python/recipe/thirdparty/providers/google.py in get_profile_info at line 58 We think it is likely that the signup API is being called twice and returning a 500 response from Google the second time, which means that the auth_code_response does not have the 'access_token' key, and instead returns the following error: { error: 'invalid_grant', error_description: 'Bad Request' } We have looked at this thread https://discord.com/channels/603466164219281420/1113510798736752692 and its related GH issue (https://github.com/supertokens/supertokens-auth-react/issues/707) but haven't been able to come up with a solution. We also cannot reliably reproduce this error. Could we get some support / should the API be catching this to avoid the KeyError? Thank you in advance!
j
r
+3
  • 5
  • 67
  • 56
I'm getting this error: SuperTokens core threw an error for a POST request to path: '/recipe/session...
k

kbanman

over 2 years ago
I'm getting this error: SuperTokens core threw an error for a POST request to path: '/recipe/session/regenerate' with status code: 400 and message: The user payload contains protected field My code looks like this:
await session.mergeIntoAccessTokenPayload({ sessionHandle: session.getHandle() });
How can I go about debugging this?
k
r
  • 2
  • 3
  • 56
hello guys! question: is there any way to include supertokens API into general swagger-based API doc...
a

art1c0

over 2 years ago
hello guys! question: is there any way to include supertokens API into general swagger-based API docs of the project? i use nest.js and connected via middleware, so maybe it's not possible or maybe you know how to do it?
a
r
  • 2
  • 5
  • 56
Previous141516Next

SuperTokens.com

SuperTokens is an open source authentication solution offering features like: Different types of login: Email / password, Passwordless (OTP or Magic link based).

Powered by