- Ya
- 5 Septemba 2026, 02:06 UTC
- Mwandishi
- Kamo
- Ahadi ya
- 082ace1
Two things went wrong on the same screen, and together they produced a settings page showing a green "Credentials complete" chip above a red "RingCentral instance 'Ring Central' is missing its Client ID". The red text was stale. A Test Connection or Sync result describes the credentials that were stored when it ran, and saving new ones does not clear it — so the operator who had just filled in the missing Client ID was still looking at the complaint about it. The server already treats a config change this way, nulling is_connected because the old verdict no longer applies; the page now does the same. The green chip was wrong. The JWT box held the RingCentral app's credentials JSON — the blob the developer console shows on the same page as the JWT, which is created separately under Credentials → JWT — and nothing checked that what was pasted could be a JWT at all. RingCentral rejected it with OAU-331 "Unparseable assertion" on every call afterwards. The box now says so as it is typed, and the same rule blocks the save on both the create and edit forms. The check is shape-only — three dot-separated base64url segments — because refusing a credential that works would be far worse than the paste it prevents; voipservice applies the same rule and is what enforces it. It lives in app/lib/voip/ so it is covered by a test that actually runs: app/settings/ is not in vitest's include list, so one written beside the component would be collected by nothing and pass by never running.