Manage integrations

The Integrations page presents you with a list of all configured integrations and lets you connect ‚ÄčAkamai MFA‚Äč with third-party systems such as identity providers (IdPs) to provide a seamless MFA service.

With identity providers (IdPs), you can create, manage, and store user identity information. This data is used to authenticate users within federated or distributed networks and grant them access to enterprise resources that they need to perform their work. ‚ÄčAkamai MFA‚Äč acts as an extra layer of security on top of the verification performed by identity platforms. End users, before they can access corporate resources, have to complete two separate identity verification processes: the primary‚ÄĒwith their IdP using their usernames and passwords, and the secondary‚ÄĒusing the ‚ÄčAkamai MFA‚Äč authentication methods (factors). Integrations with IdPs improve your organization‚Äôs security posture and provide you with a single point of maintenance of identity data for authentication purposes.

‚ÄčAkamai MFA‚Äč uses SAML 2.0 (Security Assertion Markup Language 2.0) that is an open standard for exchanging authentication and authorization data to enable single sign-on (SSO) for users. With this solution, users can access all their allowed enterprise apps with a single login.

With Integrations, you can also protect your Unix SSH and Windows local and remote logins by embedding ‚ÄčAkamai MFA‚Äč as an additional multi-factor step in third-party applications.

Additionally, you can set up a demo integration that lets you experience the ‚ÄčAkamai MFA‚Äč mobile app used by end-users to self-enroll and authenticate.

See the below table to learn about second factors and enrollment methods supported by each of the existing integrations.

Integrations

Supported authentication methods

Supported enrollment methods

  • EAA
    IdP
  • Microsoft ADFS
  • Okta
  • SAML
  • Shibboleth
  • Bypass code
  • Clientless push
  • Email or SMS OTP
  • Hardware token
  • Phone call
  • Phone security key
  • Push notification
  • Push TOTP
  • Third-party OTP devices
  • WebAuthn/FIDO2 security key
  • Email enrollment
  • In-line enrollment
  • Unix PAM
  • Windows Logon
  • Bypass code
  • Clientless push
  • Email or SMS OTP
  • Hardware token
  • Phone call
  • Push notification
  • Push TOTP
  • Third-party OTP devices

Phone security key and WebAuthn/FIDO2 security key are not supported.

  • Email enrollment

In-line enrollment is not supported.

  • PacketFence Gateway
  • Bypass code
  • Hardware token
  • Phone call
  • Push TOTP
  • Push notification
  • SMS OTP
  • Third-party authenticator app as OTP device

Phone security key and WebAuthn/FIDO2 security key are not supported.

Depending on your VPN equipment, this integration supports different use cases that let you onboard new users with:

  • Email enrollment
  • In-line enrollment

Did this page help you?