Migrations/neko
1
0
Fork 0
mirror of https://github.com/m1k1o/neko.git synced 2026-11-03 00:11:48 -06:00
Code Issues Packages Projects Releases Wiki Activity

docs: info about supporting only one provider at a time. #505

Browse Source
This commit is contained in:
Miroslav Šedivý
2025-04-07 22:44:59 +02:00
parent a46cb0536b
commit c1ccae4ac4
1 changed files with 4 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
webpage/docs/configuration/authentication.md
+4
View File
@@ -80,6 +80,10 @@ import TabItem from '@theme/TabItem';
Member providers are responsible for deciding whether given credentials are valid or not. This validation can either be done against a local database or an external system.
:::info
Currently, Neko supports configuring only one authentication provider at a time. This means you must choose a single provider that best fits your deployment needs.
:::
### Multi-User Provider {#member.multiuser}
This is the **default provider** that works exactly like the authentication used to work in v2 of neko.