-
-
Notifications
You must be signed in to change notification settings - Fork 435
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: no applicable key found in the JSON Web Key Set #5186
Comments
Console backend login no longer reports an error, but the return value from Machine-to-Machine application requesting Machine-to-Machine is:
|
Hi @cong5 , could you please elaborate on your setup and how you make M2M requests? |
first request https://xxx.shop/oidc/token get access_token: second request any Logto Management API response this error. |
Are you using a self-hosted OSS version? or you are using Logto Cloud. |
|
Did you or someone with access to your Logto localhost change the |
I can not reproduce your issue on my machine. I started a brand new OSS Logto instance with a new DB, created a m2m app, can hence successfully get the access token and access the management API. It could be helpful if you can provide a step by step guide to reproduce this issue. |
You can also check whether you have assigned the scope |
Hello!
I ran logto in kubernetes using the docker image: svhd/logto:latest, but when I tried to log into the console, an error occurred and I was unable to log in.
Oops! Something went wrong.
f: no applicable key found in the JSON Web Key Set
at c.getKey (https://xxxx.shop/console/index.b0698af2.js:3:29786)
at https://xxxx.shop/console/index.b0698af2.js:3:30333
at #c (https://xxxx.shop/console/index.b0698af2.js:3:44747)
at o.getKey (https://xxxx.shop/console/index.b0698af2.js:3:44304)
at async u (https://xxxx.shop/console/index.b0698af2.js:3:16240)
at async a (https://xxxx.shop/console/index.b0698af2.js:3:14004)
at async a (https://xxxx.shop/console/index.b0698af2.js:3:18868)
at async l (https://xxxx.shop/console/index.b0698af2.js:3:40765)
at async c.verifyIdToken (https://xxxx.shop/console/index.b0698af2.js:1:532057)
at async c.handleSignInCallback (https://xxxx.shop/console/index.b0698af2.js:1:530082)
The text was updated successfully, but these errors were encountered: