- 19 Apr 2023
- 1 Minute to read
- Contributors
- Print
- DarkLight
- PDF
Two-Factor Authentication (2FA)
- Updated on 19 Apr 2023
- 1 Minute to read
- Contributors
- Print
- DarkLight
- PDF
For additional security more and more organisations have a corporate policy that requires so-called Two-Factor Authentication aka 2FA (Wikipedia), also for cloud applications like Cirrus.
Cirrus' SAML 2.0 Single Sign-On integration enables organisations to integrate the Cirrus Platform with their existing Identity Provider with Two-Factor Authentication.
As an example, an organisation may use Azure Active Directory (AAD) to give it's users access to all its cloud applications like Office365 (which relies on AAD), Blackboard, Gmail. With Two-Factor Authentication enforced in Azure Active Directory and access to their cloud applications via Azure Active Directory, all their cloud applications are behind Two-Factor Authentication.
Office365 relies on AAD for user access management so if your organisation already uses Office365 it would fit the example.
In the example above we have:
- Identity Provider with SAML 2.0 and Two-Factor Authentication support
- Service Providers (Cloud applications) with SAML 2.0 support
If you and your organisation is interested in Two-Factor Authentication, refer them to this page and our SAML 2.0 Single Sign-On (SSO). That contains all info to set it up. No action from Cirrus is required!
Most modern Identity Providers support both SAML 2.0 and Two-Factor Authentication, a small selection of well-known examples:
- Microsoft Azure Active Directory (also used by Office 365)
- Microsoft Active Directory through Microsoft Active Directory Federation Services
- Citrix
- Google Workspace
- Amazon Cognito
- SAP
(Additionally there are a multitude of Open Source alternatives available, e.g. RedHat IM, Gluu, OpenIAM, ...)