TikTok V5 + Security
This commit is contained in:
@@ -39,6 +39,8 @@
|
||||
- Optional helper: `TIKTOK_ADMIN_KEY` for guarding the `/api/tiktok/connect` start route.
|
||||
- OAuth result: access/refresh tokens are stored in the database after `/api/tiktok/connect` and `/api/tiktok/callback`.
|
||||
- Do not put TikTok access tokens in `.env`; the cron job reads them from the DB through the app flow.
|
||||
- Configure `TIKTOK_EXPECTED_OPEN_ID` for QRMaster before deploying the hardened routes. The callback and every API call fail closed when it is missing or belongs to another account.
|
||||
- `GET /api/tiktok/token` is status-only and never returns access or refresh tokens. Automations must call the server upload route instead of caching credentials locally.
|
||||
- For cron posting, use the same QRMaster server environment that already contains `CRON_SECRET` / `INTERNAL_API_SECRET` for internal APIs.
|
||||
|
||||
## TikTok Connection Status + Credential Locations
|
||||
|
||||
Reference in New Issue
Block a user