Security
Tokens
Section titled “Tokens”| Do | Don’t |
|---|---|
| Project JWT in the end-user app | kfxs_… or kfx_… in the app or NEXT_PUBLIC_* / EXPO_PUBLIC_* |
| Service token only on a server | Log service tokens or commit them |
| PAT for MCP and admin scripts | Share one PAT across untrusted machines without rotation |
Platform tokens and service tokens bypass Kallax access rules. Anyone who has them can read and write collections the endpoints expose.
On every user-owned collection, for each enabled method:
requireAuthuserFieldComparemapping_users._idto an owner field (authorId,userId, …)- File rules on upload
Empty rules mean allow unless the server sets STRICT_ACCESS_RULES. Do not rely on “auth is on” alone.
Seed authorId from the logged-in user in the client and enforce it with rules so a caller cannot set another user’s id.
Declare real contentType and size when opening an upload session. Pair fileSizeLimit / fileMimeType / fileExtensionAllow with the global size cap.
Browser apps may call /api/p/... directly. Treat every collection endpoint as public to the internet, gated only by tokens and rules.