You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Supporting rate limiting based on JWT claims will enable more granural rate limiting -- it will be possible to use information about an authenticated user.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
If a user configures a JWT Policy https://docs.nginx.com/nginx-ingress-controller/configuration/policy-resource/#jwt-using-local-kubernetes-secret and also a rate limit policy https://docs.nginx.com/nginx-ingress-controller/configuration/policy-resource/#ratelimit , currently, it is not possible to use JWT claims (like sub) as a rate limiting key.
Supporting rate limiting based on JWT claims will enable more granural rate limiting -- it will be possible to use information about an authenticated user.
Here is an example of such rate limiting in the native NGINX Plus configurtion -- https://www.nginx.com/blog/authenticating-api-clients-jwt-nginx-plus/#Leveraging-JWT-Claims-for-Logging-and-Rate-Limiting
Related: #4417
Beta Was this translation helpful? Give feedback.
All reactions