[feature]: support for authenticated API calls

[LeoSpyke]

Starting from version 0.14.0, Frigate introduced the support for authenticated UI and API interactions, thus deprecating the old endpoint (exposed on port 5000).

Leaving such port open is a security flaw that now can be natively solved without relying on 3rd party tools (like Authelia or other proxies) for authentication but still, this tool does not support authenticated HTTP calls yet.

Anyway, I really appreciate what you are doing, it saved my life (and home) 💪

[OldTyT]

Hi!
Thanks for the issue.
I researched and found out that authentication is probably still in development and has not reached its endpoint.
Because:

• There is no documentation for the endpoint /api/login
• At the beginning of the api documentation page, it is indicated:

A web server is available on port 5000 with the following endpoints.

Currently, authorization works as follows:

• We send a POST request to the /api/login endpoint with the data {"user": "USERNAME", "password": "PASSWORD"}
• We receive data from the server in cookies:
  
• Then, using the received token in cookies, we set it in headers and make a request
  

It's too confusing(

A request to add HTTP digest authorization has been created - blakeblackshear/frigate#13297

Therefore, I suggest waiting a couple of months and seeing what will be changed.

@LeoSpyke

[OldTyT]

Hurray! The description of the authorization API appeared in 0.15.0 beta 1. Docs
We are waiting...