Releases: ReachFive/CartridgeSFCC
20.8.2
Bug Fix - Remove id_token from SFCC session
Description:
Previously, id_token from reach5 login return was put into session.privacy.id_token.
This can break SFCC session limit because some provider give pictureUrl with more than 2000 characters.
Target Audience:
This fix is useful for social login.
20.8.1
New Feature: Split Korean User Names into First and Last Name for KakaoSync
Description:
Previously, during Kakao social login, only the full_name attribute was retrieved, with no differentiation between first and last names. This feature introduces the ability to automatically split the full_name into first_name and last_name fields, improving data usability for customers.
How to Use:
A new customer preference named enableKakaoTalkNameSplit has been added to enable this feature. By default, the rule splits the full_name as follows:
The first character is placed in the last_name field.
The remaining characters are placed in the first_name field.
Target Audience:
This feature is ideal for customers using Kakao social login who need to store and manage first and last names separately in their systems.
20.8.0
New Features 💪
Feature 1: Handling Null Consents
Description: This new feature allows for the proper management of null consents in the ReachFive-Synchronization job. When a consent field is set to null, it is now ignored in the request payload, thus avoiding errors during API calls to ReachFive.
How to Use: Consent fields such as custom.isNewsletter will be automatically managed, whether they are set to true, false, or null.
Target Audience: This feature is intended for administrators and developers using the ReachFive cartridge to synchronize data between SFCC and ReachFive.
Feature 2: User Deletion Synchronization
Description: This feature automatically synchronizes user deletions between ReachFive and SFCC. When a user is deleted in ReachFive, this deletion is replicated in SFCC, ensuring perfect consistency of user data.
How to Use: The synchronization is done automatically via a webhook triggered when a user is deleted in ReachFive.
Target Audience: SFCC platform administrators who want to maintain consistent user data synchronization.
Feature 3: Phone Number Update via Synchronization
Description: This feature allows updating users' phone numbers and sending a verification SMS via the ReachFive-Synchronization job.
How to Use: Brands can trigger the phone number update by setting the appropriate preferences in SFCC.
Target Audience: Developers and administrators looking to automate phone number updates and verification via SMS.
Feature 4: Allow Phone Number Registration During Signup ([ENH][Signup])
Description:
Previously, phone numbers were not registered in the ReachFive (R5) account when performing a signup if ReachFiveFastRegister was set to No. This feature allows users to enter their phone number during signup, regardless of the ReachFiveFastRegister setting.
How to Use:
The showAuth widget has been updated to include a new optional field for the phone number.
Target Audience:
This feature is beneficial for anyone who wants to collect phone numbers during signup, even if ReachFiveFastRegister is disabled.
Feature 5: Prevent Redirect to External Domains After Login (SFRA & SiteGenesis)
Description:
Previously, SFRA and SiteGenesis would redirect users to potentially malicious external domains after a successful login using ReachFive CIAM. This feature ensures that login redirects only occur within the approved higher-order domain(s) configured for your ReachFive instance.
How to Use:
No action is required from you. The updated ReachFive controller behavior automatically verifies the target URL before redirection.
Target Audience:
This feature benefits users of SFRA and SiteGenesis integrations with ReachFive CIAM.
Feature 6: Destroy Session When Unlinking Last Social Provider Identity (StoreFront)
Description:
This feature mimics the behavior of the ReachFive CIAM app. When the last social provider identity is unlinked from a user's profile, the user profile is removed from ReachFive and the session on the storefront is destroyed. This prevents unauthorized access after the social identity removal.
How to Use:
No action is required from you. This functionality is implemented automatically in the latest version.
Target Audience:
This feature benefits users of the ReachFive CIAM integration with StoreFront.
Improvements 💪
Customer Feedback-Based Improvement: Refactoring of API calls to use tokens generated by oauthToken, thus enhancing the security and consistency of API calls.
User Experience Improvement: Addition of a custom parameter to control the propagation of user deletions from SFCC to ReachFive, simplifying user deletion management.
Bug Fix 1: Update Customer Profile via Webhooks ([WEB HOOKS])
Description:
This update addresses an issue where customer profile updates in ReachFive were not being propagated to SFCC using webhooks.
Target Audience:
This fix benefits users who rely on webhooks to synchronize customer profile data between ReachFive and SFCC.
Bug Fix 2: Correct Locale Retrieval in SFCC SiteGenesis (Bugfix: La locale n'est pas correctement récupérée dans SFCC SiteGenesis)
Description:
This bug fix resolves an issue where the locale was not being correctly retrieved from SFCC SiteGenesis. This ensures that emails and other UI elements display in the appropriate language.
Target Audience:
This fix benefits users of SFCC SiteGenesis with ReachFive integration.
Bug Fix 3: Default Values for Custom Preferences (Bugfix: Les custom preferences n'ont plus de valeur par défaut)
Description:
This bug fix addresses an issue where custom preferences in the SFCC cartridge (version 20.7.0) were not populated with default values. This ensures that essential configuration options are set correctly.
Target Audience:
This fix benefits new users of the SFCC cartridge (version 20.7.0) and potentially users of previous versions who may have encountered this issue.
Bug Fix 4: Display Login Error Message During SFRA Login Flow ([SFRA] Display the error message when an error occurs during the login flow)
Description:
This bug fix addresses an issue where login error messages from ReachFive were not displayed to users during the SFRA login flow. Now, informative error messages are displayed, improving the user experience.
Target Audience:
This fix benefits users of the SFRA integration with ReachFive CIAM.
Bug Fix 5: Add asterisk on the confirm email field in the edit form
Description:
The field is mandatory and generate error when is empty, so we add the asterisk to indicate the mandatory condition.
Target Audience:
This fix benefits users of the SFRA integration with ReachFive CIAM.
20.7.1
Evolutions included in the 20.7.1 release:
Bugfix 1 : Fix the refresh token bug when we edit our profile after 5 minutes
Description: This bug occurs when a profile update is attempted more than 5 minutes after authentication. In this case, an error message appears indicating that the five-minute legitimacy limit has expired. The user is then prompted to log out and log back in to verify their identity.
Evolutions included in the 20.7.0 release:
- [Improvement] Refresh token for link/unlink SLO
- [Improvement] Scheduling initialization of the UI SDK
20.7.0
20.6.1
Evolutions included in the 20.6.1 release:
- [Improvement] Manage the password update or reset from 'My account'
- [Improvement] Authorize a SLO profile to update their profile
- [Fix] Error 'Access token invalid or expired' that occured on the update password feature for the Social Login mode
- [Fix] Replace the default value used as a temporary password by the recommended SFCC Pipelet
ResetCustomerPassword - [Fix] Define the right attributes in the call of the function createReachFiveCustomer
20.5.0
Evolutions included in the 20.5.0 release:
- Get the SFCC locale and set the locale attribute in the Core SDK and UI SDK initialization
- Set the SFCC login with the profile's email (if it’s provided) during a Social Login signup flow. Enabled using the custom preference
isReachFiveEmailAsLogin - Retrieve the provider access token from ReachFive oauth/token during a Social Login authentication. Enabled using the custom preference
isReachFiveReturnProviderToken - Store the query param
datain the customer profile (the query param can be set at the beginning of the signup flow, and it transits until the end of the authentication flow)
