@@ -1367,8 +1367,15 @@ Limiting Login Attempts
13671367
13681368 Login throttling was introduced in Symfony 5.2.
13691369
1370- Symfony provides basic protection against `brute force login attacks `_.
1371- You must enable this using the ``login_throttling `` setting:
1370+ Symfony provides basic protection against `brute force login attacks `_ thanks to
1371+ the :doc: `Rate Limiter component </rate_limiter >`. If you haven't used this
1372+ component in your application yet, install it before using this feature:
1373+
1374+ .. code-block :: terminal
1375+
1376+ $ composer require symfony/rate-limiter
1377+
1378+ Then, enable this feature using the ``login_throttling `` setting:
13721379
13731380.. configuration-block ::
13741381
@@ -1452,16 +1459,8 @@ You must enable this using the ``login_throttling`` setting:
14521459
14531460 The ``login_throttling.interval `` option was introduced in Symfony 5.3.
14541461
1455- Internally, Symfony uses the :doc: `Rate Limiter component </rate_limiter >`
1456- which by default uses Symfony's cache to store the previous login attempts.
1457- However, you can implement a :ref: `custom storage <rate-limiter-storage >`.
1458-
1459- In order to work, the Rate Limiter component must be installed in your
1460- application by running the following command:
1461-
1462- .. code-block :: terminal
1463-
1464- $ composer require symfony/rate-limiter
1462+ The Rate Limiter component uses by default the Symfony cache to store the previous
1463+ login attempts. However, you can implement a :ref: `custom storage <rate-limiter-storage >`.
14651464
14661465Login attempts are limited on ``max_attempts `` (default: 5)
14671466failed requests for ``IP address + username `` and ``5 * max_attempts ``
0 commit comments