Change Details

Using the mechanism from {T399198}, we should add rate limiting information to every session JWT. The current OAuth 2 JWTs use an integer "number of requests per hour" value, but that's very inflexible, so we'll probably add some sort of rate limiting class instead, and use configuration (puppet, I guess) to translate that to specific numbers in Varnish / Envoy. This task is to define where that rate limiting class should come from.

Using the mechanism from {T399198}, we should add rate limiting information to every session JWT (to be used by {T405544}). The current OAuth 2 JWTs use an integer "number of requests per hour" value, but that's very inflexible, so we'll probably add some sort of rate limiting class instead, and use configuration (puppet, I guess) to translate that to specific numbers in Varnish / Envoy. This task is to define where that rate limiting class should come from.

Using the mechanism from {T399198}, we should add rate limiting information to every session JWT (to be used by {T405544}). The current OAuth 2 JWTs use an integer "number of requests per hour" value, but that's very inflexible, so we'll probably add some sort of rate limiting class instead, and use configuration (puppet, I guess) to translate that to specific numbers in Varnish / Envoy. This task is to define where that rate limiting class should come from.