Open Lucisu opened 3 months ago
When using Laravel's RateLimiter, the attempts are stored globally instead of separately per tenant.
Execute in the first tenant:
RateLimiter::attempt( 'key', 100, function () { return true; }, 60*60 );
In the second tenant, you can see that the remaining attempts is 99 instead of 100:
RateLimiter::remaining( 'key', 100 );
Like the Cache calls, I think that RateLimiter calls should be separated by the tenant.
11.9
3.8
What bootstrappers do you have enabled?
The default ones from 3.8, nothing changed
Does enabling the RedisTenancyBootstrapper fix this?
Bug description
When using Laravel's RateLimiter, the attempts are stored globally instead of separately per tenant.
Steps to reproduce
Execute in the first tenant:
In the second tenant, you can see that the remaining attempts is 99 instead of 100:
Expected behavior
Like the Cache calls, I think that RateLimiter calls should be separated by the tenant.
Laravel version
11.9
stancl/tenancy version
3.8