Apply Rate Limiting to Critical Routes Using SlowAPI

[LEVIII007]

We need to apply rate limiting to specific critical routes in our FastAPI application to prevent potential abuse or exploitation. The rate limiter should be configured using SlowAPI and applied selectively on routes that handle sensitive actions like authentication and token generation.

Task Details:

Global Initialization of SlowAPI:

Initialize the SlowAPI rate limiter instance globally in main.py.
Set up a global exception handler for rate limiting to return appropriate error messages (e.g., status code 429 for "Too Many Requests").
Apply Rate Limiting to Critical Routes:

Import the limiter instance in specific router files where rate limiting is needed.

Add rate limiting on:

/auth/create-access-token: Limit to 2 requests per second.
/auth/refresh-token: Limit to 2 requests per second.
/user/create: Limit to 10 requests per second.
Review other routes that handle sensitive actions and determine if they need rate limiting.
Testing:

Ensure that the rate limiting works as expected for these routes.
Verify that the system returns appropriate error messages when the rate limit is exceeded.

Why This Is Important:

Prevent potential abuse of sensitive endpoints like token generation.
Ensure the application remains responsive by mitigating overload due to excessive requests.