Dashboard API key issue
# support-questions-legacyn
nkshah2
05/11/2023, 9:58 AM@bradvrm
Moving this to a separate thread
b
bradvrm
05/11/2023, 9:59 AMthank you, Let me post some screenshots of my set up/what i'm seeing
n
nkshah2
05/11/2023, 9:59 AMWhat version of SuperTokens core are you using?
nkshah2
05/11/2023, 10:01 AMAlso yeah, screenshots would be great
b
bradvrm
05/11/2023, 10:02 AMInterestingly just noticed the payload is empty on this call, should it contain the API key that i'm trying to validate?
n
nkshah2
05/11/2023, 10:02 AMThere should be an Authorization header
nkshah2
05/11/2023, 10:02 AMThe payload for this is supposed to be empty
b
bradvrm
05/11/2023, 10:03 AMahh yes, i can see the key as "bearer " under authorization header
n
nkshah2
05/11/2023, 10:04 AMis it just
bearerb
bradvrm
05/11/2023, 10:04 AMbradvrm
05/11/2023, 10:04 AMyeah sorry contains the key
bradvrm
05/11/2023, 10:04 AMfor supertokens core, i'm using the latest image from registry.supertokens.io/supertokens/supertokens-postgresql in docker
n
nkshah2
05/11/2023, 10:08 AMOne sec, going to try and see if I can recreate this
b
bradvrm
05/11/2023, 10:08 AMno problem, thank you 🙂
n
nkshah2
05/11/2023, 10:41 AMHey we have identified a bug thats causing this problem and will be releasing a fix for this soon (https://github.com/supertokens/supertokens-node/pull/561). The catch here is that it will be fixed for the latest SDK version which would be a breaking change for you (13.6.0 -> 14.0.1)
You can either update to the latest SDK version once its released to continue using API keys or you can use email password based auth (refer to our docs for this) and stay on 13.6.0
b
bradvrm
05/11/2023, 10:42 AMno problem. i'll use username/pword for now and then update once 14.0.1 is released. Thank you for looking into that 🙂
n
nkshah2
05/11/2023, 10:43 AMHappy to help
24 Views