Dashboard API key issue
# support-questions-legacy
n
@bradvrm Moving this to a separate thread
b
thank you, Let me post some screenshots of my set up/what i'm seeing
n
What version of SuperTokens core are you using?
Also yeah, screenshots would be great
b
Interestingly just noticed the payload is empty on this call, should it contain the API key that i'm trying to validate?
n
There should be an Authorization header
The payload for this is supposed to be empty
b
ahh yes, i can see the key as "bearer " under authorization header
n
is it just
bearer
or does it contain your API key after the bearer as well?
b
yeah sorry contains the key
for supertokens core, i'm using the latest image from registry.supertokens.io/supertokens/supertokens-postgresql in docker
n
One sec, going to try and see if I can recreate this
b
no problem, thank you 🙂
n
Hey 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
no problem. i'll use username/pword for now and then update once 14.0.1 is released. Thank you for looking into that 🙂
n
Happy to help
23 Views