opensource/filament
3
0
Fork 0
mirror of https://github.com/filamentphp/filament.git synced 2026-09-24 15:42:09 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: Document app authentication cache requirements (#20474)

Browse Source 
* docs: Document app authentication cache requirements

Co-authored-by: Amp <amp@ampcode.com>

* docs: Use warning for app authentication cache requirements

Co-authored-by: Amp <amp@ampcode.com>

---------

Co-authored-by: Amp <amp@ampcode.com>
This commit is contained in:
Dan Harrin
2026-09-09 10:42:41 +01:00
committed by GitHub
co-authored by Amp
parent c990885d6c
commit f013f7ae15
1 changed files with 4 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/07-users/02-multi-factor-authentication.md
+4
View File
@@ -82,6 +82,10 @@ public function panel(Panel $panel): Panel
}
```
<Aside variant="warning">
To prevent the same app authentication code from being accepted more than once, use a default cache store that supports atomic locks, such as the database or Redis cache driver. All application servers must use the same cache backend. With other cache configurations, concurrent requests may accept the same code more than once.
</Aside>
### Setting up app recovery codes
If your users lose access to their two-factor authentication app, they will be unable to sign in to your application. To prevent this, you can generate a set of recovery codes that users can use to sign in if they lose access to their two-factor authentication app.