https://supertokens.com/ logo
Join Discord
Powered by
Using HTTP API Gateway to host `/auth` Supertokens...
# support-questions-legacy
e
Using HTTP API Gateway to host 
/auth
Supertokens route. We are trying to create an authorizerbut get the error:
Copy code
Invalid issuer: https://{http api gateway id}.execute-api.us-east-1.amazonaws.com/auth. No public key has been found with this issuer.
I think this is something new because we were able to create in Authorizer in Http API gateway against the 
/auth
endpoint proivded by Supertokens few months ago. Any thoughts?
r
Hey.
What’s the issuer value that’s configured on the aws console? And what’s the iss claim value in the JWT?
e
> What’s the issuer value that’s configured on the aws console? I'm not sure what the "issuer value" is. Here is the console interface. I've removed the actual API Gateway ID (also in the error message). > And what’s the iss claim value in the JWT? At this point, I don't think a JWT is involved.
I feel that supertokens Auth endpoint is running because if I try to access an invalid path for the Issuer URL we get the error "Issuer must have a valid discovery endpoint ended with '/.well-known/openid-configuration'". So, that is being discovered when using the correct Issuer URL.
r
can you provide an example access token here please?
e
What access token?
r
hmm sorry. Misunderstood
can you DM me the actual URL?
e
DMed
r
hey
so the issue seems to be that you have the wrong value of apiDOmain configured on yourbackend
PreviousNext
Powered by