The platform save dropped every KamoPBX field client-side

Fixkamo-internal
Shipped
August 27, 2026 at 3:00 PM UTC
Author
Kamo
Commit
a7ad320

Entering the credentials in the UI reported success and changed nothing. systemConfigApi.update serialises an explicit allowlist rather than the caller's object, so the seven kamoPbx fields never left the browser — SecurityService never even received a request. This is the third allowlist in the same path. Adding a column to SystemConfiguration means touching all three: this one, the controller's UpdateBody, and its toDto. Missing any one fails silently in a different place. Three tests pin it, including that the '***' keep-sentinel survives — dropping or rewriting it would overwrite the master credential on every save.

All changes

Like what you see shipping?

Every one of these updates lands in your workspace automatically. Start free and watch it grow week after week.

Start Free ForeverView Pricing