fix: base64-encode Patchmon Basic auth credentials server-side #77

Merged

josh merged 5 commits from dev into main 2026-05-30 19:04:27 -04:00

Conversation 0 Commits 5 Files Changed 4

+11 -3

5 Commits

Author	SHA1	Message	Date
josh	72b8d60985	Merge pull request 'Merge pull request 'test: add failing tests for sort/order on GET /api/instances' (#71) from dev into main' (#76) from merge/main-into-dev-v1.7.1 into dev ... Reviewed-on: #76	2026-05-30 19:03:24 -04:00
josh	917fb26e05	Merge branch 'main' into dev — resolve 1.7.0/1.7.1 version overlap, keep 1.7.1 ... # Conflicts: # package.json	2026-05-30 19:00:49 -04:00
josh	a28867b398	Merge pull request 'fix: base64-encode Patchmon Basic auth credentials server-side' (#74) from fix/patchmon-sync-basic-auth into dev ... Reviewed-on: #74	2026-05-30 18:54:53 -04:00
joshandClaude Opus 4.7	ac71ea2c49	chore: bump to version 1.7.1 ... Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-30 18:51:27 -04:00
joshandClaude Opus 4.7	efa1750cac	fix: base64-encode Patchmon Basic auth credentials server-side ... Patchmon's API uses standard RFC 7617 Basic auth — `Basic base64(token_key:token_secret)`. The handler was sending the api_token field verbatim, so it only worked if the user had manually base64-encoded the credential. After a Patchmon upgrade, the sync started returning HTML (the SPA, served when auth is rejected) and failing with "Unexpected token '<'" on JSON.parse. Now: if the token contains ':' (raw key:secret), encode it server-side; otherwise pass through unchanged for backward compatibility. UI gets a placeholder hint showing the expected format. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-30 18:33:41 -04:00