BigCommerce API Authentication is a process where users can login to their external application with BigCommerce website credentials.
miniOrange’s BigCommerce API authentication plugin performs the BigCommerce API integration and enables BigCommerce to serve as an IDP (Identity Provider), allowing users to access various applications and external websites with a Single Sign-On (SSO).
Users will authenticate themselves via their BigCommerce credentials and once they successfully integrate with BigCommerce API they can access all the external applications.
The BigCommerce User database is linked to miniOrange user store to provide support for BigCommerce API SSO into external multiple applications.This use case can be achieved by BigCommerce API Authentication plugin which provides SSO login security using BigCommerce API endpoints.
User Authentication: | https://api.bigcommerce.com/stores/<YOUR-STORE_HASH>/v3/customers/validate-credentials |
Header: | Header Name: X-Auth-Token Header Value: <Your Acess token from BigCommerce API> |
Method: | POST |
User Authentication Parameters: | { "email": ##username##, "password": ##password##, "channel_id": 1 } |
Status: | error |
Status Method: | message |
Service Provider Name | Choose appropriate name according to your choice |
SP Entity ID or Issuer | Your Application Entity ID |
ACS URL X.509 Certificate (optional) | Your Application Assertion Consumer Service URL |
NameID Format | Select urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress |
Response Signed | Unchecked |
Assertion Signed | Checked |
Encrypted Assertion | Unchecked |
Group policy | Default |
Login Method | Password |
Client Name | Add appropriate Name |
Redirect URL | Get the Redirect-URL from your OAuth Client |
Descrption | Add if required |
Group Name | Default |
Policy Name | As per your Choice |
Login Method | Password |
Note: Choose the Authorization Endpoint according to the identity source you configure.
In case you are setting up SSO with Mobile Applications where you can't create an endpoint for Redirect or Callback URL, use below URL.
https://login.xecurify.com/moas/jwt/mobile
You have a choice to set multiple IDPS for Single Application, i.e integrate multiple IDP and users can select IDP accordingly from which they want to authenticate themselves. There are three different ways to authenticate users using IDP.
Note : At once you can select either of them.
Few usecases where customers configure multiple IDPs -
For Cloud IDP - | https://login.xecurify.com/moas/discovery?customerId=<customer_id> |
For On-Premise IDP - | https://yourdomain.com/discovery?customerId=<customer_id> |
You can see the screenshot below of the IDP Selection Page with a list of IDPs .
Note: To view the IDP in drop-down list, go to Identity Providers tab > against your configured IDP > Select >Edit , here Enable the Show IdP to Users option.
If you have multiple IDPs and you want a certain set of users to authenticate from one IdP whereas another set of users to authenticate from another IdP, based on their email domains then you can achieve this by using the following steps:- Our domain mapping feature
For your reference , Azure AD and Okta is being used as two different IDPs and WordPress is being used as SP. Follow the guides to set up Okta and WordPress at your end.
If you have multiple IDPs (identity provider) and you want a certain application user to authenticate with one IDP and other application users with another IDP then you can achieve this by our Identity Source Feature.
Related Pages:-
What is Identity Brokering?
Login with WordPress API
Configure BigCommerce as Authentication source