MIDAS SAML 2.0 (SSO) Integration SAML 2.0: Frequently Asked Questions

Which Identity Providers are supported?

Technically, any Identity Provider which supports SAML 2.0 should be supported.

Popular SAML 2.0 Identity Providers include (but are not limited to):

  • Auth0
  • Microsoft ADFS
  • Microsoft Entra ID (formerly Azure AD)
  • Okta
  • OneLogin
  • PingFederate
  • PingOne SSO
  • Shibboleth
We provide a SAML Test Tool which you can use to test SAML 2.0 integration with your preferred Identity Provider.

Why must my MIDAS be licensed for "Unlimited" users in order to use SAML 2.0 integration?

If your MIDAS system was licensed for a finite number of users, then SAML 2.0 integration would potentially exclude some of your SAML 2.0 users from accessing the software - defeating the point of the seamless "single-sign on" ability offered by SSO integration.

For example, if your MIDAS system is only licensed for 5 users, and your organization's Identity Provider recognizes 10 user account, then whichever five users authenticate via your Identity Provider first, they would then be the only 5 users who could continue to access your MIDAS booking system in the future - all others would be rejected.

Therefore, to avoid this, we have restricted SAML 2.0 integration to customers with "Unlimited" users licenses.

You can quickly upgrade to "Unlimited" users at any time via mid.as/upgrade