feat(files): API tokens — a machine reaches the library folder by folder
A user can make a token for a machine of theirs (`/api/tokens`, signed-in only): `sfl_` + 32 random bytes + a checksum, only its SHA-256 kept, shown once. Sent as a Bearer header it is honoured on six `/api/files` routes only — folders, list, file, hash, upload, delete — and there only in the folders its grants name, with the rights they give (list / read / write / delete). One check, `FilesCaller.may`, in every route; a folder or file out of reach answers like a missing one; the files shared with the user are never in reach. A token beats a cookie on the same request. The Hub preset makes the user's one Hub folder (a new folder kind) and grants it every right. Refused tokens are slowed down per client, a runaway machine per token; last use is stamped at most once a minute; making and revoking a token is audited, and a token's uploads and deletes name it in their audit rows.
This commit is contained in:
@@ -31,5 +31,7 @@
|
||||
"file_folder_create": "Mappa létrehozva",
|
||||
"file_folder_rename": "Mappa átnevezve",
|
||||
"file_folder_retention": "Mappa megőrzési ideje módosítva",
|
||||
"file_folder_delete": "Mappa törölve"
|
||||
"file_folder_delete": "Mappa törölve",
|
||||
"api_token_create": "API-token létrehozva",
|
||||
"api_token_revoke": "API-token visszavonva"
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user