chris/frigate
1
0
Fork 0
forked from Github/frigate
Code Pull Requests Packages Activity

add setting for secure flag on cookie (#11422)

Browse Source 
* add setting for secure flag on cookie

* docs fix
This commit is contained in:
Blake Blackshear
2024-05-18 14:53:49 -05:00
committed by GitHub
parent 3ce8816b9a
commit 402f5fa142
4 changed files with 18 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/docs/configuration/authentication.md
View File

@@ -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

3
docs/docs/configuration/reference.md
View File

@@ -73,6 +73,9 @@ auth:
reset_admin_password: False
# Optional: Cookie to store the JWT token for native auth (default: shown below)
cookie_name: frigate_token
# Optional: Set secure flag on cookie. (default: shown below)
# NOTE: This should be set to True if you are using TLS
cookie_secure: False
# Optional: Session length in seconds (default: shown below)
session_length: 86400 # 24 hours
# Optional: Refresh time in seconds (default: shown below)