Skip to content

JWT Authentication Fails with "401 Invalid Signature" #7128

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

Open
1 task done
yang-wang11 opened this issue Feb 14, 2025 · 0 comments
Open
1 task done

JWT Authentication Fails with "401 Invalid Signature" #7128

yang-wang11 opened this issue Feb 14, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@yang-wang11
Copy link

yang-wang11 commented Feb 14, 2025

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

Our team is currently using KIC 2.9 with Kong 3.3(dbless mode), and we suspect that a large number of KongConsumers is causing authentication failures.

We have 6,912 KongConsumers, but even though both KongConsumers and corresponding Secrets are correctly configured, requests with valid JWTs are being rejected with a "401 Invalid Signature"

I suspect that KIC is unable to handle such a large number of KongConsumers and fails to sync(deck) them properly to Kong. To verify this, I queried the Admin API at $url/jwt, but the response only contained a limited number of JWT credentials, rather than the expected full set.

Expected Behavior

  • Requests with valid JWTs should be authenticated successfully.
  • Kong should be able to handle and sync all 6,912 KongConsumers correctly.
@yang-wang11 yang-wang11 added the bug Something isn't working label Feb 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant