Need Help? We are right here!
Thanks for your Enquiry.
If you don't hear from us within 24 hours, please feel free to send a follow-up email to info@xecurify.com
Search Results:
×
BigCommerce Social Login allows customers to create an account or log in to your BigCommerce store using their existing social media credentials, such as Apple, Facebook, Google, or Twitter. This makes the registration & login process quicker & more convenient for customers, as they do not need to create a new account & remember additional login information.
With BigCommerce Social Login SSO features, you can:
Verified Technology Partner of BigCommerce
Social Login Support for any BigCommerce Plan (Standard, Plus, Pro, Enterprise)
miniOrange offers free help through a consultation call with our System Engineers to Install or Setup BigCommerce SSO solution in your environment with 30-day free trial.
For this, you need to just send us an email at idpsupport@xecurify.com to book a slot and we'll help you in no time.
miniOrange provides user authentication from various external sources, which can be Directories (like ADFS, Microsoft Active Directory, OpenLDAP, AWS etc), Identity Providers (like Microsoft Entra ID, Okta, AWS), and many more. You can configure your existing directory/user store or add users in miniOrange.
Please make sure your organisation branding is already set under Customization >> Login and Registration Branding in the left menu of the dashboard.


Note: In BigCommerce, the API Path is the base URL that your application or integration uses to connect to your store’s data through BigCommerce APIs. The Store Hash is a unique identifier automatically generated by BigCommerce for each store. It appears in the API Path.

Note: This Store Hash will be required while configuring BigCommerce in miniOrange.





| Display Name [Required] | BigCommerce (According to your choice) |
| Redirect-URL [Required] | Storefront URL/login/token/ |
| Client ID | Copy from the downloaded file in Step 1 |
| Client Secret | Copy from the downloaded file in Step 1 |
| Access Token | Copy from the downloaded file in Step 1 |
| Description | According to your choice |
How to Get the Redirect URL from BigCommerce
Your Redirect URL should be: <Storefront URL>/login/token/


| Subject | E-Mail Address. |
| Signature Algorithm | HS256 |
| Logout URL | Copy the storefront URL as mentioned above and append /login.php?action=logout e.g., https://{{my-store}}.mybigcommerce.com/login.php?action=logout |

| Primary Identity Provider | The identity source against which user will be authenticated |
| Force Authentication | Enable if you want user to authenticate even if the user has a session |
| Enable User Mapping | Enable if you are sending the logged-in user from this app in the response |



| Attribute Name | Attribute Type | Attribute Value |
|---|---|---|
| store_hash | Custom Attribute Value | Refer to Step 1 above. |
| redirect_to | Custom Attribute Value | Endpoint where you wish to redirect the user to after sso. [Homepage or account page e.g. /account.php] |
| operation | Custom Profile Attribute | customer_login |
| first_name | External Idp Attribute | first_name |
| last_name | External Idp Attribute | last_name |
| External Idp Attribute |

To synchronize address, custom attributes, and form fields from the Identity Provider (IDP) to BigCommerce, the following details must be configured:
Address Fields
To successfully sync customer address information, the following attributes are required:
In the below diagram, we are using miniOrange as the IDP.

| Attribute Name | Attribute Type | Value |
|---|---|---|
| addresses.first_name | First Name | - |
| addresses.last_name | Last Name | - |
| addresses.address1 | Custom Profile Attribute | address1 |
| addresses.city | Custom Profile Attribute | city |
| addresses.state_or_province | Custom Profile Attribute | state/province |
| addresses.country_code | Custom Profile Attribute | country |
| addresses.postal_code | Custom Profile Attribute | postal_code |

Note: When sending the country value, always use the country code (e.g., US, IN). If you pass the full country name such as “United States”, the value will not be updated — only country codes are supported for correct mapping.
While syncing address fields, ensure that the city, state, and country values you provide are valid options supported by BigCommerce and exist in their respective dropdown lists.

For the Sign up form fields:

| Attribute Name | Attribute Type | Value |
|---|---|---|
| addresses.first_name | First Name | - |
| addresses.last_name | Last Name | - |
| addresses.address1 | Custom Profile Attribute | address1 |
| addresses.city | Custom Profile Attribute | city |
| addresses.state_or_province | Custom Profile Attribute | state/province |
| addresses.country_code | Custom Profile Attribute | country |
| addresses.postal_code | Custom Profile Attribute | postal_code |
| form_fields.name.0 | Custom Attribute Value | Law School |
| form_fields.value.0 | Custom Attribute Value | XYZ |
| form_fields.name.1 | Custom Attribute Value | Bar Exam State |
| form_fields.value.1 | Custom Attribute Value | Arizona |
| form_fields.name.2 | Custom Attribute Value | Bar Exam Date |
| form_fields.value.2 | Custom Attribute Value | 31-12-2025 |
| form_fields.name.3 | Custom Attribute Value | Estimated Graduation Month |
| form_fields.value.3 | Custom Attribute Value | January |
| form_fields.name.4 | Custom Attribute Value | Estimated Graduation Year |
| form_fields.value.4 | Custom Attribute Value | 2025 |


For the Attribute Fields

| Attribute Name | Attribute Type | Value |
|---|---|---|
| color | Custom Profile Attribute | blue |
| customer_address | Custom Profile Attribute | MG road |
| customer_mobile | Custom Profile Attribute | +911234567890 |
| DOB | Custom Profile Attribute | 2002-01-01 |
| attribute_string 01 | Custom Profile Attribute | testing |


NOTE: Update customer profile during sso

For ExternaI Identity Provider
| Attribute Name | Attribute Type | Value |
|---|---|---|
| addresses.first_name | External Idp Attribute | first_name |
| addresses.last_name | External Idp Attribute | last_name |
| addresses.address1 | External Idp Attribute | address1 |
| addresses.city | External Idp Attribute | city |
| addresses.state_or_province | External Idp Attribute | state/province |
| addresses.country_code | External Idp Attribute | country |
| addresses.postal_code | External Idp Attribute | postal_code |

Note: When sending the country value, always use the country code (e.g., US, IN). If you pass the full country name such as “United States”, the value will not be updated — only country codes are supported for correct mapping.
While syncing address fields, ensure that the city, state, and country values you provide are valid options supported by BigCommerce and exist in their respective dropdown lists.

For the Sign up form fields:

| Attribute Name | Attribute Type | Value |
|---|---|---|
| form_fields.name.0 | Custom Attribute Value | Law School |
| form_fields.value.0 | External Idp Attribute | XYZ |
| form_fields.name.1 | Custom Attribute Value | Bar Exam State |
| form_fields.value.1 | External Idp Attribute | Arizona |
| form_fields.name.2 | Custom Attribute Value | Bar Exam Date |
| form_fields.value.2 | External Idp Attribute | 31-12-2025 |
| form_fields.name.3 | Custom Attribute Value | Estimated Graduation Month |
| form_fields.value.3 | External Idp Attribute | January |
| form_fields.name.4 | Custom Attribute Value | Estimated Graduation Year |
| form_fields.value.4 | External Idp Attribute | 2025 |


For Custom Attribute Fields

| Attribute Name | Attribute Type | Value |
|---|---|---|
| color | External Idp Attribute | blue |
| customer_address | External Idp Attribute | MG road |
| customer_mobile | External Idp Attribute | +911234567890 |
| DOB | External Idp Attribute | 2002-01-01 |
| attribute_string 01 | External Idp Attribute | testing |


NOTE: Update customer profile during sso

miniOrange provides user authentication from various external sources, which can be Directories (like ADFS, Microsoft Entra ID, OpenLDAP, Google, AWS Cognito etc), Identity Providers (like Okta, Shibboleth, Ping, OneLogin, KeyCloak), Databases (like MySQL, Maria DB, PostgreSQL) and many more. You can configure your existing directory/user store or add users in miniOrange.




























https://{{branding}}.xecurify.com/moas/broker/login/jwt/{customerID}/google_oauth?client_id=yourclientID&redirect_uri=https://storeurl.bigcommerce.com/login/token/https://{{branding}}.xecurify.com/moas/broker/login/jwt/{customerID}/facebook_oauth?client_id=yourclientID&redirect_uri=https://storeurl.bigcommerce.com/login/token/https://{{branding}}.xecurify.com/moas/broker/login/jwt/{customerID}/linkedin_oauth?client_id=yourclientID&redirect_uri=https://storeurl.bigcommerce.com/login/token/https://{{branding}}.xecurify.com/moas/broker/login/jwt/{customerID}/appleid_oauth?client_id=yourclientID&redirect_uri=https://storeurl.bigcommerce.com/login/token/







Yes, we support SSO into BigCommerce using Microsoft Entra ID, Okta and Auth0 credentials.
If the user does not exist in your bigcommerce store, our SSO solution will automatically create the user on bigcommerce and perform a seamless login.
Yes, we support social login providers such as google, facebook, twitter and many more. You can set up your Social login app by following the guide here : https://www.miniorange.in/iam/login-with-external-idp/
miniOrange BigCommerce Social Login SSO solution is available for all BigCommerce plans, including the free ones. We also offer support for a wide range of social login providers, including Google, Facebook, Twitter, and more. With our solution, customers can easily log in to their BigCommerce accounts using their preferred social media credentials, while website owners can benefit from increased engagement & streamlined login processes.