Skip to content

Portal authentication (Metaswitch, Broadworks)

On deployments for Metaswitch or Broadworks service providers, users can sign in to MiaRec with the credentials of their carrier portal account: MiaRec forwards the submitted login and password to the portal for verification instead of checking a local password. This avoids separate MiaRec passwords for large carrier-managed user bases.

Flag-gated features

These options are hidden by default. They appear under Administration › User Authentication only when the corresponding feature flag is enabled — Metaswitch integration or Broadworks integration — see Advanced settings. Enable them only on deployments for the respective platform.

Metaswitch CommPortal

Administration › User Authentication › Metaswitch CommPortal, then Edit Configuration:

  • Enable Metaswitch CommPortal based user authentication;
  • CommPortal URL — the customer-facing CommPortal address;
  • Test connection settings — a CommPortal username and password used only for testing; click Test a Connection to verify MiaRec can authenticate against the portal.

Broadworks Web Portal

Administration › User Authentication › Broadworks Web Portal, then Edit Configuration:

  • Enable Broadworks Web Portal based user authentication;
  • Broadworks Web Portal URL — in the format https://portal.example.com;
  • Test connection settings — a Web Portal username and password for testing, with Test a Connection.

Enabling portal sign-in for users

Once a portal integration is enabled, the corresponding option — Metaswitch CommPortal or Broadworks Web Portal — appears in the Authenticate with choices on user accounts (and in the Authentication type of user auto-provisioning). Set it per user or via Bulk Edit; the user's MiaRec Login must match their portal account. Portal sign-ins are password-based from MiaRec's point of view, so two-step verification can apply to them like regular password sign-ins.