From 24b11ad71b007727b10f6c9ec5a8511f5a81d0e0 Mon Sep 17 00:00:00 2001 From: Blake Blackshear Date: Sat, 18 May 2024 14:41:24 -0500 Subject: [PATCH] docs fix --- docs/docs/configuration/authentication.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/docs/configuration/authentication.md b/docs/docs/configuration/authentication.md index ae7230c84..168959bee 100644 --- a/docs/docs/configuration/authentication.md +++ b/docs/docs/configuration/authentication.md @@ -18,11 +18,11 @@ Frigate supports two modes for authentication Frigate stores user information in its database. Password hashes are generated using industry standard PBKDF2-SHA256 with 600,000 iterations. Upon successful login, a JWT token is issued with an expiration date and set as a cookie. The cookie is refreshed as needed automatically. This JWT token can also be passed in the Authorization header as a bearer token. -Users are managed in the UI under Settings > Authentication. +Users are managed in the UI under Settings > Users. #### Onboarding -On startup, an admin user and password are generated and printed in the logs. It is recommended to set a new password for the admin account after logging in for the first time under Settings > Authentication. +On startup, an admin user and password are generated and printed in the logs. It is recommended to set a new password for the admin account after logging in for the first time under Settings > Users. #### Resetting admin password