The platform save dropped every KamoPBX field client-side

Fixkamo-internal
Ya
27 Agosti 2026, 15:00 UTC
Mwandishi
Kamo
Ahadi ya
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.

Mabadiliko yote

Je, unaona nini kuhusu usafiri?

Kila moja ya hizi updates ardhi katika nafasi yako ya kazi moja kwa moja. Kuanza bure na kuangalia kukua wiki baada ya wiki.

Kuwa Huru MileleMtazamo wa bei