From eacf790309f979865dc0959c4a637278e48f376e Mon Sep 17 00:00:00 2001 From: Blake Blackshear Date: Sat, 18 May 2024 11:26:15 -0500 Subject: [PATCH] Update docs/docs/configuration/authentication.md Co-authored-by: Nicolas Mowen --- docs/docs/configuration/authentication.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/configuration/authentication.md b/docs/docs/configuration/authentication.md index f74faec4d..975c10214 100644 --- a/docs/docs/configuration/authentication.md +++ b/docs/docs/configuration/authentication.md @@ -16,7 +16,7 @@ Frigate supports two modes for authentication ### Native mode -Frigate stores user information in it's 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. +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 be managed under at Settings > Authentication.