Skip to content

Commit 2c81d29

Browse files
Add a section on authentication throttling (laravel#9600)
* Add a section on authentication throttling * wording * note instead of warning * formatting --------- Co-authored-by: Taylor Otwell <[email protected]>
1 parent 387f697 commit 2c81d29

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

fortify.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -205,6 +205,15 @@ Fortify::authenticateThrough(function (Request $request) {
205205
});
206206
```
207207

208+
#### Authentication Throttling
209+
210+
By default, Fortify will throttle authentication attempts using the `EnsureLoginIsNotThrottled` middleware. This middleware throttles attempts that are unique to a username and IP address combination.
211+
212+
Some applications may require a different approach to throttling authentication attempts, such as throttling by IP address alone. Therefore, Fortify allows you to specify your own [rate limiter](/docs/{{version}}/routing#rate-limiting) via the `fortify.limiters.login` configuration option. Of course, this configuration option is located in your application's `config/fortify.php` configuration file.
213+
214+
> [!NOTE]
215+
> Utilizing a mixture of throttling, [two factor authentication](/docs/{{version}}/fortify#two-factor-authentication), and an external web application firewall (WAF) will provide the most robust defense for your legitimate application users.
216+
208217
<a name="customizing-authentication-redirects"></a>
209218
### Customizing Redirects
210219

0 commit comments

Comments
 (0)