• Home
• Integrations
• MFA
• Two-Factor Authentication (2FA) for Webflow

Webflow two-factor authentication (2FA)

---

Webflow two-factor authentication (2FA) is an additional layer of security in which a user is prompted to provide two factors to gain access to the Webflow account. With Webflow 2FA being enabled, anyone trying access your Webflow account from an unrecognized computer/device must provide additional authorization. Authentication starts with a user submitting his traditional username and password. Once the user successfully gets authenticated with the 1st step verification, configured 2FA (OTP verification, Push Notifications, YubiKey, TOTP, Google Authenticator etc) method prompts for 2nd-step verification.

miniOrange provides 15+ authentication methods and solutions for Webflow. It allows users and organizations to set up certain authentication and settings which includes password restrictions, restricting sign-in methods, as well as other security settings.

With miniOrange Webflow 2FA solution, you can:

• Choose from popular authenticators such as Google Authenticator, Microsoft Authenticator and more.
• Enable Passwordless login for your Webflow Account.
• Prevent unauthorized person from accessing the resources even if cyber attackers get to know your credentials.
• Connect easily with any external identity source like Azure AD, ADFS, Cognito, etc.

Follow the Step-by-Step Guide given below for Webflow two-factor authentication (2FA) :

1. Configure Webflow in miniOrange:

• Login into miniOrange Admin Console.



• Go to Apps and click on Add Application button.



• In Choose Application, select JWT from the application type dropdown.



• In the next step, search for Webflow application from the list. If your application is not found, search for JWT App and you can set up your Application.



• You can configure the following details in the application:

  Display Name	Enter the Display Name (i.e. the name for this application)
  Redirect URL	Enter the Redirect URL (i.e. the endpoint where you want to send/post your JWT token). You can add multiple redirect URLs by separating them with a ‘;’.E.g. abc.com;xyz.com
  Client ID	The Client ID is shown in the field below. Click the clipboard icon to copy it.
  Client Secret	Client Secret is hidden by default. Click the eye icon to reveal it and use the clipboard icon to copy it. This is used in the HS256 signature algorithm for generating the signature.
  Description (Optional)	Add a description if required.




• Click Save.
• You will be redirected to the Policies section.



• Click on the Assign group button. A new Configure Group Assignment Modal will open.
  • Assign Group: Select the groups you want to link with the application. You can select up to 20 groups at a time.
  
  
  
  • If you need to create new group. Click on Add New Group button.
  • Enter the Group name and click on Create Group.
  
  
  
  • Click on Next.
  • Assign Policies: Add the required policies to the selected groups. Enter the following details:
  • First Factor: Select the login method from the dropdown.
  • If you select Password as the login method, you can enable 2-Factor Authentication (MFA) and Adaptive Authentication, if needed.
  • If you select Password-less as login method, you can enable 2-Factor Authentication (MFA) if needed.
  • If you select Magic Link as the login method, the following options appear:
  • Enable sign-in from other IPs: When enabled, users can open the Magic Link from a different IP address than the one from which it was requested.
  • Enable sign-in from other devices: When enabled, users can open the Magic Link on a different device than the one used to request it.



• Click on Save. Policies will be created for all the selected groups.
• You will see the policy listed once it’s successfully added.



• Click on Advanced tab.
• Enter the following details as required:

  Access Token	Enter the access token that will be sent to your redirect URL after a user logs in. This token helps your app know the user is allowed to access certain features.
  ID Token Expiry (In Mins)	Set how long (in minutes) the ID token will be valid. After this time, the user will need to log in again to get a new token.
  Subject	Choose what information, like the user’s email address, will be used to identify them in the token. This helps your app know which user is logged in.
  Signature Algorithm	Select your signature algorithm from the dropdown.
  The Logout URL of your application	Enter the web address where users should be sent after they log out.
  Enable Shared Identity	This feature lets you control whether a specific application can be accessed by shared user or not.




• Signature Algorithms for JWT

RSA-SHA256

• Asymmetric, uses a set of private and public keys to generate and validate the signature which is included in the JWT token.
• The private key is used to generate the signature on the IDP side.
• The public key is used to verify the signature on the SP side.
• We provide the public key for this.



HS256

• Symmetric, uses the same secret key to generate and validate the signature
• The secret key in this case is configurable from the app configuration page.
• Switch to Login options tab.

  Primary Identity Provider	Select the default ID source from the dropdown for the application. If not selected, users will see the default login screen and can choose their own IDP. [Choose miniOrange in this case.]
  Force Authentication	If you enable this option, users will have to log in every time, even if their session already exists.
  Enable User Mapping	Enable this option, if you want the app to show which user is signed in when it responds.
  Show On End User Dashboard	Enable this option if you want to show this app in the end-user dashboard.




• Navigate to Endpoints and copy the following details:



• Single Sign-On URL:
  • This URL is used to initiate user authentication to obtain the JWT token.
  • Take redirect_uri as one of the query parameters.
  • After successful authentication on the IDP end, an active user session is created in the IDP and the user is redirected to the redirect_uri with the JWT token.
• Single Logout URL:
  • This URL is used to log out the user from the IDP by removing the active user session.
  • Take redirect_uri as one of the query parameters.
  • After removing the active user session, the IDP redirects the user to the redirect_uri.
• Reply back URL for IdP initiated logout:
  • This URL is used to initiate the logout in case the JWT user login was IDP Initiated [User logged in to the dashboard
    first and then initiated the login for the app from the dashboard.]
  • After logging out the user from the IDP, the user is redirected to the IDP dashboard login page.

2. Adding Script on Webflow's End

• To enable SSO on Webflow's end, all you need to do is add a customized script.
• Click here to download the script needed or you can reach out to us at idpsupport@xecurify.com at any time if you need help with the integration.

3. Configure 2FA for Webflow

3.1: Enable 2FA for Users of Webflow app

• To enable 2FA for Users of Webflow application. Go to Policies >> App Login Policy
• Click on Edit icon against the application you have configured.



• Check the Enable 2-Factor Authentication (MFA) option.



• Click on Submit.

3.2: Configure 2FA for your Endusers

• To enable 2FA/MFA for webflow endusers, go to 2-Factor Authentication >> 2FA Options For EndUsers.
• Select default Two-Factor authentication method for end users. Also, you can select particular 2FA methods, which you want to show on the end users dashboard.
• Once Done with the settings, click on Save to configure your 2FA settings.

3.3: Enduser 2FA Setup

• Login to End-User Dashboard using end user login URL.
• For Cloud Version: The login URL (branding url) which you have set.
• For On-Premise version: The login URL will be the same as of Admin Login URL.
• Select Setup 2FA from left panel. Then select any of the 2FA method available.
• For now, we have selected the SMS >> OTP OVER SMS as our 2FA method. You can explore the guide to setup other 2FA methods here.
• Enable the OTP over SMS if you have your phone number added under your account information else click on Edit >> Click here to update your phone number link.



• In Account Information, click on edit icon.



• Select your country code, enter your mobile number, and click Send OTP.



• Enter the OTP sent to your phone and click Validate.



• After adding your phone number, turn on the toggle to activate OTP over SMS.



• Now Enable 2 Factor Authentication toggle if not done before as shown below.

4. Test 2FA for Webflow

a. If 2FA for for End-user is configured

• Go to your Webflow Domain. It will redirect you to miniOrange Single Sign-On Service console.



• Enter your login credentials, and click on login. It will prompt to verify yourself against the configured 2fa method.
  e.g. If you have configured OTP over SMS, after login into Webflow it will prompt for OTP.



• Enter the OTP received in your phone, after successful 2fa verification, you will be redirected to the Webflow dashboard.

b. If 2FA for end-user is not enabled

• You will be prompted to register for 2Fa for end-user. It's a one time process.
• Configure your basic details.



• Configure any authentication method of your choice.



• After successful registration, you will be logged in to your Webflow account.


Not able to configure or test MFA?


Contact us or email us at idpsupport@xecurify.com and we'll help you setting it up in no time.

5. Adaptive Authentication with Webflow

Adaptive Authentication for Webflow enables administrators to enforce context-aware access policies by evaluating user login conditions such as IP address, device, location and login time. Based on the configured policy, users can be allowed access, challenged with additional verification or denied access. Administrators can also configure email alerts, customize user-facing error messages, review policy settings before deployment and assign adaptive authentication policies to application login policies to strengthen security and prevent unauthorized access.

[Note: The Adaptive Authentication section has been moved from the left navigation menu. You can now access and manage adaptive authentication policies by navigating to Policies >> Adaptive Access Policy.]

A. Restricting access to Webflow with IP Based Access Restriction

IP Based Access Restriction allows administrators to control user access based on the source IP address of the login request. Administrators can configure trusted or restricted IP addresses and IP ranges and define the action to be taken when a user's IP address matches the configured criteria. During authentication, the user's IP address is evaluated against the configured policy and access is either Allowed, Denied or Challenged based on the selected configuration.

You can configure Adaptive Authentication with IP Based Restriction in following way :

• Login to Self Service Console >> Policies >> Adaptive Access Policy section from the left side menu.



• Click on the Create Policy button on the upper right. Add a suitable policy name and click on Create Policy.



• Expand the IP Based Access Restriction section by clicking on the dropdown icon to configure IP-based access rules.



• Click Add IP Range to configure IP addresses or IP ranges for the policy.



• Specify the IP Address that you want to whitelist. For the IP Range other than the whitelisted one, you can select the above setting to reflect.
• Choose either Allow or Deny by selecting the corresponding option from the dropdown. If a user tries to login with the whitelisted IP address, they will always be allowed access.
• We support IP address range in three formats i.e., IPv4, IPv4 CIDR and IPv6 CIDR. You can choose whichever is suitable for you from the dropdown menu.
• You can add multiple IPs or IP ranges by clicking the + Add IP Range button.



• Once the changes are made, click on Next.
• Select Action for Behavior Change, choose the appropriate Action and Challenge Type for the user from that section.




Action for behavior Change Options :




Attribute	Description
Allow	Allow users to authenticate and use services if Adaptive authentication condition is true.
Deny	Deny user authentications and access to services if Adaptive authentication condition is true.
Challenge	Challenge users with one of the three methods mentioned below for verifying user authenticity.




Challenge Type Options:




Attribute	Description
User second Factor	The User needs to authenticate using the second factor he has opted or assigned for such as OTP over SMS PUSH Notification OTP over Email and many more.
KBA (Knowledge-based authentication)	The System will ask the user for 2 of 3 questions he has configured in his Self-Service Console. Only after the right answer to both questions is the user allowed to proceed further.
OTP over Alternate Email	User will receive an OTP on the alternate email they have configured through the Self Service Console. Once the user provides the correct OTP, they are allowed to proceed further.



• Click on Next to continue.

B. Restricting access to Webflow with Device Based Access Restriction

Device Based Access Restriction allows administrators to control user access based on trusted and registered devices. By leveraging device identification and verification mechanisms, administrators can define policies that evaluate the device used during authentication. When a user attempts to log in, the device is assessed against the configured policy and the appropriate action: Allow, Challenge or Deny is applied based on the configured conditions.

You can configure Adaptive Authentication with Device Based Restriction in following way :

• Login to Self Service Console >> Policies >> Adaptive Access Policy section from the left side menu.



• Click on the Create Policy button on the upper right. Add a suitable policy name and click on Create Policy.



• Click on the Dropdown option to expand the Device Based Access Restriction section to configure device-based access controls.



• Turn on the Enable Device Configuration toggle.



• Configure either Agentless Device Restriction or Agent-Based Device Restriction based on your organization's requirements.
• Agentless Device Restriction: Verifies and manages trusted devices without requiring any software or agent installation on the endpoint. It uses browser and device-based identification methods to evaluate device trust and enforce access policies during authentication.
• Agent-Based Device Restriction: Provides enhanced device trust verification by using a lightweight agent installed on managed devices. It enables advanced device validation and risk-based access control to ensure that only trusted devices can access protected resources.



• Click here to get more information about Device Based Restriction.
• Once the changes are made, click on Next.
• Under Action for Behaviour Change, select the appropriate action and challenge type for the policy.



• Click on Next to continue.

C. Restricting access to Webflow with Location Based Access Restriction

In location restrictions, admin configures a list of locations where they want to allow end-users to either login or deny based on the condition set by the admin. When a user tries to login with adaptive authentication enabled, their Location Attributes, such as (Latitude, Longitude and Country Code) are verified against the Location list configured by the admin. Based on this user will be either allowed, challenged or denied.

You can configure Adaptive Authentication with Location Based Restriction in following way :

• Login to Self Service Console >> Policies >> Adaptive Access Policy section from the left side menu.



• Click on the Create Policy button on the upper right. Add a suitable policy name and click on Create Policy.



• Click on the Dropdown to expand the Location Based Access Restriction section to configure location-based access rules.



• Select Register Location if User Completes Challenge to automatically register a user's location after successful challenge verification.
• Click on Add Location.



• In the Search Location field, enter the location name and select the appropriate location from the search results.
• Specify the radius around the selected location and choose the distance unit (KM or Miles). This will be the total area in and around the location we have configured using the Latitude and Longitude points.
• For each configured location, select whether access should be Allowed or Denied.



• You can click on the Add Location button to add more than one location and then follow steps 2-4 as mentioned above.
• Once the changes are made, click on Next.
• Select your Action for behavior Change and Challenge Type for user from the Action for behavior Change Section.



• Click on Next to continue.

D. Restricting access to Webflow with Time Based Access Restriction

In time restriction, admin configures a time zone with Start and End Times for that timezone and users are either allowed, denied or challenged based on the condition in the policy. When an end-user tries to login with the adaptive authentication enabled, their time zone-related attributes such as Time-Zone and Current System Time, are verified against the list configured by the admin and based on the configuration, the user is either allowed, denied or challenged.

You can configure Adaptive Authentication with Time Based Restriction in following way :

• Login to Self Service Console >> Policies >> Adaptive Access Policy section from the left side menu.



• Click on the Create Policy button on the upper right. Add a suitable policy name and click on Create Policy.



• Expand the Time Based Access Restriction section by clicking on the dropdown icon to Time Based Access Restriction rules.



• Enter the Login Window Buffer Time (Minutes) to allow a grace period before the start time and after the end time of the configured login window. If no value is specified, the default buffer time of 0 minutes is applied.
• Click Add Time to create a time-based access rule.



• Select the required Timezone, configure the Start Time and End Time and choose the applicable days.
• For each time-based rule, select whether access should be Allowed or Denied.



• Click on the Add Time to add more than one timezones.
• Once the changes are made, click on Next.
• Select your Action for behavior Change and Challenge Type for user from the Action for behavior Change Section.



• Click on Next to continue.

E. Email Alerts and Custom Email Message

This section handles the notifications and alerts related to Adaptive Access Policy. It provides the following options:

• Send email alerts: Configure the recipients who should receive email notifications when adaptive authentication events occur. Alerts can be sent to administrators, end users or both, depending on your monitoring and security requirements.
• Send email alerts to administrators: Enable this option to notify administrators when configured adaptive authentication events are triggered. You can optionally specify an email address under Administrator's e-mail address to receive alerts to receive alerts; otherwise, alerts are sent to the default administrator account.



• Send email alerts to end users: Enable this option to notify end users when adaptive authentication events affect their login attempts or device registrations.
• Number of Device Registrations Exceeded Allowed Count: When enabled, end users receive an email notification if they attempt to register more devices than the maximum number allowed by the configured device restriction policy. (Available only for end-user notifications.)



• Get email alerts if users login from unknown devices or locations: Admins need to enable this option to enable receiving alerts for different alert options.



Option	Description
Users login from unknown IP addresses, devices or locations	Enabling this option allows you to login from unknown IP addresses or devices and even locations.
Challenge Completed and Device Registered	Enabling this option allows you to send an email alert when an end-user completes a challenge and registers a device.
Challenge Completed but Device Not Registered	Enabling this option allows you to send an email alert when an end-user completes a challenge but do not registers the device.
Challenge Failed	Enabling this option allows you to send an email alert when an end-user fails to complete the challenge.





• In case you want multiple admin accounts to receive alerts, then you can enable the option for admin and then enter the admin emails separated by a ',' in the input field next to Administrator's email to receive alerts label. To enable alerts for the end users, you can enable the End User checkbox.
• In case you want to customize the deny message that the end user receives in case his authentication is denied due to adaptive policy, you can do this by entering the message inside Deny Message text box.

F. Review

Review the configured policy conditions, behavior change actions, email alert settings and custom error messages before creating the adaptive authentication policy. This step provides a consolidated view of all configured settings, allowing you to verify the policy configuration and make any necessary changes before saving.




• Click on Create Policy.

G. Add Adaptive Authentication policy to Webflow

• Login to Self Service Console >> Policies >> App Login Policy.
• Click on Edit icon option for predefined app policy.



• Set your policy in the Policy Name and select Password as First Factor.



• Enable Adaptive Authentication on Edit Login Policy page and select the required restriction method as an option.
• From Select Login Policy dropdown select the policy we created in last step.
• Apply Restrictions Using: Configure how multiple adaptive authentication restrictions should be evaluated during user login.
  • AND: All enabled restrictions must be successfully satisfied for the login attempt to be allowed.
  • OR: At least one enabled restriction must be successfully satisfied for the login attempt to be allowed.



• Adaptive Authentication Restrictions: Configure additional login restrictions and verification conditions to strengthen account security and control user access based on contextual risk factors.
  • IP Restriction: Restrict login access to specific IP addresses or IP ranges for enhanced security.
  • Device Restriction: Allow login access only from trusted or pre-authorized devices.
  • Location Restriction: Control user login access based on geographic location.
  • Time Restriction: Restrict user login access to specific days or time periods.
  • Force MFA On Each Login Attempt: Require users to complete MFA verification during every login attempt regardless of device or session state.

How to add a trusted Device

• When End-user log in to the self service console after the policy for device restriction is on, he is provided the option to add the current device as a trusted device.

External References

• Looking for Webflow SSO solution
• More about MFA