Release notes
The release notes describe new features, enhancements, and fixes for the ReachFive platform. The latest release notes are found below. For previous releases, check out the sidebar.
For upcoming changes that require your attention, see the Attention page.
Other releases
The following shows other ReachFive releases for your convenience.
Latest version | Release page | Docs | |
---|---|---|---|
|
|||
|
|||
MavenCentral |
|||
|
|||
SFCC Cartridge |
7 November 2024 (v2.123)
ReachFive v2.123
introduces a few improvements and needed bug fixes.
We’re happy to introduce our Data Breach Detection feature.
We now retrieve an additional field from Kakao.
You can also now filter users by MFA credentials on the ReachFive Console.
As always, we made some general improvements and fixed a few items for you.
Kakao verified phone numbers
You are now able to retrieve and leverage the phone_number_verified
information from KakaoTalk.
The information below outlines what happens when users authenticate using Kakao with ReachFive.
If the phone_number
scope does not exist for the account, neither the phone_number
or phone_number_verified
fields are retrieved or valued inside the ReachFive profile for the user.
For more details, see Kakao Connect.
- SMS feature enabled
-
If the SMS feature is enabled and the
phone_number
scope exists, we retrieve thephone_number_verified
and set the boolean on their ReachFive profile to the appropriate valuetrue
if verified andfalse
if unverified. - SMS feature not enabled
-
If the SMS feature is not enabled, even if the
phone_number
scope exists,phone_number_verified
remainsfalse
.
You must enable OpenID Connect Activation on your Kakao Login application in order to retrieve the phone_number_verified
information.
Filter by MFA users
You can now filter users by those who have enrolled their identifier (email or phone number) for Multi-factor Authentication. This can help you analyse or produce reports of how many of your users are using MFA. This includes filtering by the MFA credential type, when it was created, and the phone number. Email is the email associated with the user account and is returned as normal in a search.
This is available for filtering:
-
User profiles on the ReachFive Console
-
Pre and post-event webhooks
-
With the GET
api/v2/users
endpoint using the MFA credential object.ExampleGET api/v2/users?filter=credentials.type=="email"
Example scenario
You want to get a quick reference of how many of your users have enrolled their mobile or email for MFA.
-
Go to your ReachFive Console.
-
Navigate to
. -
Click Filter.
-
In the field, type MFA and you see the options to filter by the following:
-
User - MFA - Type (Authentication)
-
User - MFA - Email - Created At
-
User - MFA - Phone Number - Created At
-
User - MFA - Phone Number - Value
See the MFA credentials object for details on each of these fields.
-
General improvements
-
We made some improvements to ensure that
external_id
is valued and retained properly in the User profile object.
Fixes
Item | Fixed |
---|---|
The |
✓ |
There were some role issues for users authenticating to the ReachFive Console with Azure. |
✓ |
There was temporarily an access issue for those using MFA on the ReachFive Console. |
✓ |
There was a brief issue with updating roles for clients in the ReachFive Console. |
✓ |
For a brief period, you could not save changes to Email templates. |
✓ |