Open

For more details, check please Upgrading/Downgrading Commitment Tier

Okta External Identity Provider

Okta is an enterprise-grade identity management service built for the cloud but compatible with many on-premises applications. With Okta, IT can manage any employee's access to any application or device. Okta runs in the cloud on a secure, reliable, extensively audited platform, which integrates deeply with on-premises applications, directories, and identity management systems.
Our platform supports integration with Okta for providing a single sign-on between the Okta identity service and your Storefront.

Open

For more details, check please Okta (OIDC)

Displaying Extra Fields in “My Profile” Form

You can now include extra (custom) fields to the "My Profile" page by publishing custom fields created for the Account entity. These fields can be either editable or non-editable, depending on whether you want to gather more information from your customers or keep certain user-specific information on display.

For more details, check please Displaying Extra Fields in "My Profile" Form

Azure AD External Authentication - Enhancements

Azure AD authentication had been introduced for allowing single sign-on between your Azure AD B2C and your Storefront. In this release, we implemented new features such as attributes mapping and matching with an existing BSS Account:

• Multitenant - We better support multitenant configuration (i.e., to allow all users of any Azure AD directory to login to your Storefront) by introducing the Authority field.
  

• Attributes Mapping:  We have introduced an easy way to map the JSON response of the identity provider to a Property of the BSS Account/Contact/User. You can also map a field with more than one field separated with a comma "," and the priority with which they are written applies (if no value is found for the first field, the code checks the second).

• Matching using the “Account Code” Field: There will be a check via the identity provider's response on whether an account exists under the Azure Portal with that specific account code or not. If a match is found between a BSS account and an identity provider's account, then the registration process will be skipped. However, if no match is found, then register on our systems is required.

For more details, check please

Azure AD B2C External Authentication - Enhancements

Azure AD B2C authentication was introduced to allow single sign-on between your Azure AD B2C and your Storefront. In this release, we implemented the following features:

• Introduce of Authority field for complying with OIDC protocol.
  
  

• Default values for Attributes mapping. We introduced default values for mapping BSS attributes to the JSON response of the identity providers.

For more details, check please

NetSuite Connector - Support for Token-Based Authentication

NetSuite has announced that from version 2021.1, the Token-Based Authentication will become mandatory. We have updated our NetSuite connector to support the new authentication mechanism for complying with the NetSuite request. For more details, check please

Resolved Issues