Refactor demo login as an authentication method
Use the authentication method system for the demo login and the generated accounts. This makes it possible to toggle it off on production systems as these shouldn't have it enabled at all.
This commit is contained in:
parent
a33c8e9dac
commit
0d0e38e4b6
14 changed files with 212 additions and 141 deletions
|
@ -20,6 +20,12 @@ Time in seconds before a session is deleted from the client and server, resultin
|
|||
|
||||
This should be several times greater that `NUXT_SESSION_ROTATES_TIMEOUT`.
|
||||
|
||||
### NUXT_AUTH_DEMO_ENABLED
|
||||
|
||||
Boolean indicating if the demo authentication provider should be enabled. This allows logging in using only a name with no additional checks or security and should _never_ be enabled on a production system. The purpose of this is to make it easier to demo the system.
|
||||
|
||||
Defaults to `false`.
|
||||
|
||||
### NUXT_TELEGRAM_BOT_TOKEN_FILE
|
||||
|
||||
Path to a file containing the token for the Telegram bot used for authenticating users via Telegram.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue