DL6ER e3c4dcf215 Restructure API response from /history/clients and /history/database/clients to allow for sparse data. ...

Add new config option webserver.api.client_history_global_max controling if the activities chart should sort and show the *global* (integrated over 24 hours) or the `local` (measured individually in each time slot) most active clients
Allow setting webserver.api.maxClients to 0 to always return all clients in /api/history/clients

Signed-off-by: DL6ER <dl6er@dl6er.de>

2024-02-16 17:15:20 +01:00

..

json

!!! BREAKING CHANGE !!! Switch to the proven memory-hard password-hashing alogorithm BALLOON. The stored password hash will be upgraded on the first successdful login. To wave the necessity to implement BALLOON with every client trying to access the API, we remove the existing challenge-response authentication in favor of allowing login straight with the password. This has been avoided in the past, however, seems now acceptable that FTL (even by default) offers secure end-to-end encryption over HTTPS.

2023-05-30 21:22:45 +02:00

libs

Restructure API response from /history/clients and /history/database/clients to allow for sparse data.

2024-02-16 17:15:20 +01:00

checkAPI.py

Update test/api/checkAPI.py

2023-11-03 06:47:32 +01:00

openapi-enforcer.js

Also allow authentication by sending SID via HEADER

2021-02-03 09:08:23 +01:00

test-rate-limit.py

Add rate-limiting on password login attempts

2023-10-07 19:59:32 +02:00