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

BigCommerce Two-Factor Authentication (2FA/MFA)

---

Enabling 2FA (2-step verification) for your BigCommerce Store provides an extra level of security that goes beyond relying solely on a username & password. By introducing a second authentication factor, such as a one-time password sent via phone or email, the risk of unauthorized access to your BigCommerce store is significantly reduced. Even if an attacker manages to obtain a user's password, they would still need the second factor to gain access.
By implementing BigCommerce 2FA, merchants & users can effectively safeguard their BigCommerce store, customer data & sensitive business information from unauthorized access attempts & potential security breaches.

With miniOrange BigCommerce 2FA solution, you can:

• Choose from 15+ 2FA methods including OTP over SMS/Email, Push notification and more.
• Enable Passwordless login for your BigCommerce Store.
• 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.

Verified Technology Partner of BigCommerce

SSO + MFA Support for any BigCommerce Plan (Standard, Plus, Pro, Enterprise)

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

1. Create BigCommerce API

• Log in to BigCommerce Admin Panel.
• Go to the Settings from the menu, scroll down and select API Accounts.



• Click on Create API Account and choose Create V2/V3 API Token option from the menu shown.
• Add a suitable name for your API account.
• API Path will be used as the store_hash value when we configre BigCommerce in miniOrange which will require in step2.



• Enable the Customers option as Modify and Customers Login option as login. Keep rest of the settings as it is.
• Click on Save.



• Download the API credentials file. It contains the API token, Client ID and Client Secret.

2. Configure BigCommerce in miniOrange

• Login into miniOrange Admin Console.
• Go to Apps Click on Add Application button.



• In Choose Application Type click on Create App button in JWT application type.



• In the next step, search for BigCommerce application from the list and click on it.



• Enter the following values in the respective fields.
1. Custom Application Name [Required] : BigCommerce (According to your choice)
2. Description : According to your choice
3. Redirect-URL [Required] : Storefront URL, e.g. https://{{my-store}}.mybigcommerce.com/login/token/
4. Logout-URL : https://{{my-store}}.mybigcommerce.com
5. Force Authentication : Enable if you want user to authenticate even if the user has a session
6. Primary IDP : The identity source against which user will be authenticated
7. User Mapping : Enable if you are sending the logged-in user from this app in the response



1. Group Name : Default
2. Policy Name : Add policy name according to your Preference
3. Login Method : Password



• Click on Save.
• For Attribute Mapping, navigate to Select >> Edit next to your configured applicaition.



• If you are using an external IDP, jump to the below steps to set up external IDP.
  
• If you are using miniOrange as an IDP:
  • Enter the Client Id, App Secret and Access Token (which we have downloaded from step 1 during API creation in BigCommerce Console).
  • For Signature Algorithm, select HS-256 from the dropdown menu.
  • Set Subject to E-Mail Address.
  
  
  
  • To map the attributes between the miniOrange IDP and BigCommerce application, click on Attributes + button.
  • The first three attributes will be hard-coded values.

  Attribute Name	Attribute Value
  store_hash	You got in this step.
  redirect_to	Endpoint where you wish to redirect the user to after sso. [Homepage or account page e.g. /account.php]
  operation	customer_login

  
  
  
  
  • Click on Save.
  • Now, You can access BigCommerce Account Using IDP credentials through the Single-sign-on URL as shown in image above.
• If you are using an external IDP:
  • Enter the Client Id, App Secret and Access Token (which we have downloaded from step 1 during API creation in BigCommerce Console).
  • For Signature Algorithm, select HS-256 from the dropdown menu.
  • Set Subject to E-Mail Address.
  
  
  
  • You need to map the following attributes coming in from the idp by choosing the external IDP option.
  
  
  
  • Click on Save.
  • Now, You can access BigCommerce Account Using IDP credentials through the Single-sign-on URL as shown in image above.

3. Configure 2FA for BigCommerce

3.1: Enable 2FA for Users of BigCommerce app

• To enable 2FA for Users of BigCommerce 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 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 BigCommerce 2FA

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

• Go to your BigCommerce 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 BigCommerce it will prompt for OTP.



• Enter the OTP received in your phone, after successful 2fa verification, you will be redirected to the BigCommerce 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 BigCommerce 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 BigCommerce

A. Restricting access to BigCommerce with IP Configuration

You can use adaptive authentication with BigCommerce Single Sign-On (SSO) to improve the security and functionality of Single Sign-On. You can allow a IP Address in certain range for SSO or you can deny it based your requirements and you can also challenge the user to verify his authenticity. Adaptive authentication manages the user authentication bases on different factors such as Device ID, Location, Time of Access, IP Address and many more.

You can configure Adaptive Authentication with IP Blocking in following way :

• Login to Self Service Console >> Adaptive Authentication >> Add Policy.



• Add a Policy Name for your Adative Authentication Policy.
• Select Action for Behavior Change, click the Edit link, and then 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.
Challenge	Deny user authentications and access to services if Adaptive authentication condition is true.
Deny	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.



• Now click Edit option from the IP Configuration section to configure custom IP range.
• Select Add IP if the User's IP Address is not in the configured list.
• 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 button.



• Once the changes are made, scroll down to the end and click on Save.

B. Adaptive Authentication with Limiting number of devices

Using Adaptive Authentication you can also restrict the number of devices the end user can access the Services on. You can allow end users to access services on a fixed no. of devices. The end users will be able to access services provided by us on this fixed no. of devices.

You can configure Adaptive Authentication with Device Restriction in following way


• Login to Self Service Console >> Adaptive Authentication >> Add Policy.
• Add a Policy Name for your Adaptive Authentication Policy.
• Select your Action for behavior Change and Challenge Type for user from the Action for behavior Change Section.



• On the Add Policy tab, go to the Device Configuration section and click the Edit button.
• Enter the Number of Device Registrations Allowed as per your requirement. (2-3 devices are recommended.)
• Choose Action if number of devices exceeded (This will override your setting for Action for behavior Change.)
• Challenge: The user needs to verify himself using any of the three methods mentioned in table in step 5.1
• Deny : Deny users access to the system
• Enable Mobile Device Restriction to block logins from mobile devices. This ensures all login attempts from mobile devices will be declined.
• Enable MAC Address Based Restriction if you want to restrict access based on device MAC address.



• Scroll down to the bottom of the page and click on Save.

C. Add Adaptive Authentication policy to BigCommerce

• Login to Self Service Console >> Policies >> Add 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 and click on Submit.

D. Notification and Alert Message.

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

• 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.
Number of Device registrations exceeded allowed count	This option will allow you to register more devices than the devices you have numbered.
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.




• Next subsection is Send email alerts which allows us to enable or disable alerts for admin and end-users. To enable alerts for admins, you can enable the Administrators checkbox.



• 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.

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

• Detailed guide for BigCommerce SSO setup
• Read more about BigCommerce SSO MFA solution
• Checkout 15+ MFA methods
• What is Customer Identity and Access Management (CIAM)?
• Read more about BigCommerce Customer SSO