Allow Users to Log in to the Cloud Voice App with AD Domain Accounts

Once your directory users are synced, you can let them reach the Cloud Voice App with the same Active Directory (AD) domain account they already use elsewhere. Turning on single sign-on (SSO) removes the need for a separate extension password and gives users one credential to remember.

Before you begin

Make sure you have already connected Cloud Voice to Active Directory. SSO relies on users that have been imported through that integration.

Turn on single sign-on

1. Sign in to the PBX web portal and open Integrations > Collaboration.

2. Find the Single Sign-on (SSO) section and switch it on.

   

3. Optional: Use the Login Method drop-down to decide how AD users are allowed to authenticate.

   

   • Allow users to log in via SSO or using the PBX credential: Users may sign in either through SSO with their AD account or with the username and password of the linked extension.
   • Enforce SSO login only: Users are restricted to SSO and cannot use their extension credentials.

   Caution

   Choosing Enforce SSO login only removes the extension username and password as a sign-in path. If Active Directory becomes unreachable, or a user has no AD account, that user is locked out with no fallback. During a rollout, keep the combined option until each user has confirmed their AD login works, then switch to enforced SSO.

4. Click Save.

Result

Synced users can now sign in to the Cloud Voice App by entering their AD domain credentials directly, using the format username@domainname.

Note

To use AD sign-in on the mobile and desktop apps, users need at least these versions:

• Cloud Voice App for Android: 5.21.7 or later
• Cloud Voice App for iOS: 5.21.3 or later
• Cloud Voice App for Windows: 1.18.5 or later
• Cloud Voice App for Mac: 1.18.5 or later