BreizhVoIPIPBX Features - Telephony Solutions
SSO and Strong Authentication
Signing in with the account you already have. If your company runs Microsoft 365 or Google, your people sign in with that account: no extra password to remember, and a departure is handled in the same place as everything else. For the accounts that administer the installation, a second factor can be required: a temporary code, a physical key or a fingerprint.
How it works
- 1The user chooses to sign in with their Microsoft, Google or Infomaniak account.
- 2Their account on the platform is created or matched automatically, with nothing to type.
- 3Their company's rules apply: password policy, expiry, two-factor authentication.
- 4Two-factor authentication can also be added here: mobile app, physical key, fingerprint.
- 5When an account is disabled at Microsoft or Google, access stops here too.
Use cases
- A company already on Microsoft 365: one less password per person to manage.
- Strengthening administrator access without imposing the same constraint on everyone.
- A departure: access is cut once, in the company directory.
- An internal security policy to meet, with rules already defined elsewhere.
- Fewer password reset requests, which take up support time.
Benefits
- Sign-in with company accounts, with no extra password.
- Automatic matching: nothing to create by hand.
- Two-factor authentication by mobile app, physical key or fingerprint.
- The company's security rules apply without being redefined.
- A departure is handled in the same place as the rest of the access.
Examples
- A company on Microsoft 365: everyone signs in with their work account, and no password is created for telephony.
- The two administrators use a physical key: a stolen password opens nothing.