- Shipped
- August 26, 2026 at 1:03 AM UTC
- Author
- kamo
- Commit
- e61a1eb
Three screens, one change. The phone server's overview tab replaces "Connect with RingCentral" with the credential form the JWT flow actually needs — client id, secret, platform URL and a service-user JWT — built like the Teams one next to it. Platform URL is editable because a sandbox app's JWT is refused by production and vice versa, and pointing at the wrong host produces an invalid_grant that reads exactly like a bad credential. Secrets round-trip as "***", so editing the phone server's name does not mean re-pasting them. The platform Advanced tab loses its RingCentral card. There is no Kamo-wide RingCentral registration any more, and an operator filling one in would be entering credentials that nothing reads. Same reasoning as ADP_WFN. The member's phone-settings tab had a real bug: the provider dropdown listed only phone servers that already had a free synced extension, so a RingCentral server created minutes earlier was invisible — an empty provider list, nothing to assign, and no way to tell why. Every active phone server is listed now, and one with nothing loaded says so and offers to sync in place. Assignment also gains the number itself. Extensions carry their own DID, so the dropdown reads "101 — Ada Lovelace (+1 702 555 0134)" rather than a bare extension number, and the member's outbound caller id becomes their own line instead of the org's main number. And the RingCentral connect button becomes a JWT field: the server proves the credential before storing it and reads back which extension it resolves to, so a JWT created on a colleague's extension is flagged rather than silently registering the softphone as that colleague. The Teams card keeps its consent hop, and the softphone's prompt stops naming RingCentral at Teams users. The member card's page of hard-coded English is keyed while it is being rewritten.