Need Help? We are right here!
Bigcommerce SSO by miniOrange has developed a ready to use Single Sign-On solution for BigCommerce. BigCommerce is a SaaS eCommerce platform that allows business owners to set up an online store and sell products on the web. BigCommerce allows its users to use their existing credentials to log in to their platform using JWT (JSON Web Token). But an interface needs to be created on the existing site that can generate that JWT token and log users into BigCommerce using their existing credentials. miniOrange solves this issue and provides Single Sign-On(SSO) into BigCommerce using miniOrange or any other third party Identity providers (IDP) with ease.
BigCommerce users want a continuous and seamless access to their portal through their existing accounts. They don't wish for their users/customers to have a separate set of credentials for logging in to BigCommerce. BigCommerce provides a way for its users to allow their users/customers to log in to the platform seamlessly. But, an interface needs to be created which would allow this.
miniOrange provides an integrated solution where a logged in user's existing session can be used to log the users into BigCommerce by creating a valid JSON Web Token (JWT).
miniOrange provides user authentication from various external sources, which can be Directories (like ADFS, Microsoft Active Directory, Azure AD, OpenLDAP, Google, AWS Cognito etc), Identity Providers (like Shibboleth, Ping, Okta, OneLogin, KeyCloak), Databases (like MySQL, Maria DB, PostgreSQL) and many more.
|Custom Application Name||Choose appropriate name according to your choice.|
|Description||Add appropriate description according to your choice.|
|Redirect-URL||The Redirect URL for SSO, e.g. https://my-store.mybigcommerce.com/login/token/|
|Policy Name||Add policy name according to your Preference.|
|Client ID||The Client ID downloaded in the file from the BigCommerce dashboard.|
|Client Secret||The Client Secret downloaded in the file from the BigCommerce dashboard.|
|Client Token||The Client Secret downloaded in the file from the BigCommerce dashboard. Required when you wish to create on the fly users in Bigcommerce.|
|Signature Algorithm||Choose HS256|
|first_name||User First Name Attribute|
|last_name||User Last Name Attribute.|
|User Email Attribute.|
|operation||The operation should be i.e customer_login|
|rediect_to||The url where user will be redirected to after successful login E.g. /account will show them their account page|
|store_hash||Your store hash. Pick from the API Key configured in the above step i.e https://api.bigcommerce.com/stores/[storehash]/v3|
miniOrange provides user authentication from various external sources, which can be Directories (like ADFS, Microsoft Active Directory, Azure AD, 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.
1. Create User in miniOrange
2. Bulk Upload Users in miniOrange via Uploading CSV File.
Here's the list of the attributes and what it does when we enable it. You can enable/disable accordingly.
|Activate LDAP||All user authentications will be done with LDAP credentials if you Activate it|
|Sync users in miniOrange||Users will be created in miniOrange after authentication with LDAP|
|Backup Authentication||If LDAP credentials fail then user will be authenticated through miniOrange|
|Allow users to change password||This allows your users to change their password. It updates the new credentials in your LDAP server|
|Enable administrator login||On enabling this, your miniOrange Administrator login authenticates using your LDAP server|
|Show IdP to users||If you enable this option, this IdP will be visible to users|
|Send Configured Attributes||If you enable this option, then only the attributes configured below will be sent in attributes at the time of login|
Refer our guide to setup LDAPS on windows server.
miniOrange integrates with various external user sources such as directories, identity providers, and etc.