Skip to content

[Communication][High] Reject or implement IP-authenticated and mutual-TLS SIP accounts #111

Closed

Description

@BechsteinDigital

Severity

High

Problem

The admin UI and API advertise and persist Digest, IP-authenticated and mutual-TLS SIP accounts. The SDK adapter explicitly throws for every method except Digest. Unsupported records are accepted and later skipped by startup provisioning while the UI can remain on Connecting.

Evidence

  • custom/static-plugins/Communication/src/Infrastructure/Voice/SdkSipAccountFactory.cs:48
  • custom/static-plugins/Communication/app/admin/src/CommunicationAdminPage.vue:12

Acceptance criteria

Choose and document one path:

  • Implement IP authentication and mutual TLS with production interop tests; or
  • remove/hide unsupported methods and reject them with a clear 422 validation response.

Additionally:

  • Existing unsupported records migrate or surface an actionable error.
  • Secrets/certificates follow the repository credential-protection model.
  • UI and API expose exactly the capabilities supported by the selected provider.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions