5 December 2024 (v2.125)

ReachFive v2.125 introduces a few improvements and needed bug fixes. You can now pass locale in SMS templates. We also made some UI SDK updates.

As always, we made some general improvements and fixed a few items for you.


SMS templates locale

You can now pass the locale for a user via SMS templates for all providers including custom providers. This leverages the Custom-Locale header parameter.

For more, see SMS templates.

  • SMS standard template

  • Custom provider 

Hi {{user.given_name}}.
Your updated settings show that your locale is now {{user.locale}}. (1)
1 Pass the {{user.locale}} in the SMS message template. 
{
  "phone_number": "+33688888884",
  "template_id": "password_reset",
  "personalizations": {
     "id": "id",
     "external_id": "externalId",
     "given_name": "Max",
     "last_name": "Robertson",
     "gender": "M",
     "sms_code": "smsCode",
     "lang": "fr",
     "locale": "fr-FR", (1)
     "has_password": "boolean",
   }
}
1 In this case, locale is set to fr-FR, which is French in France.


UI SDK updates

Available from the UI SDK version 1.30.0 and higher.

As part of the initiative to help customers move to passwordless, we have introduced a new boolean called enablePasswordAuthentication available on the showAuth method.

The enablePasswordAuthentication boolean specifies whether password authentication is enabled or not.

For more details, see showAuth.enablePasswordAuthentication.


General improvements

  • We now ensure the updated_at user profile field remains unchanged after a passwordless login, aligning with the existing behaviour for password logins.

  • You no longer need to have a "fresh" access token to use the Identity API: List MFA credentials endpoint.


Fixes

Item Fixed

The User event ID was missing in some webhook responses.

✓

Some customers were receiving errors in the OaaS flow during Third-party authentication when users were already logged in through First-party.

✓

In some limited instances, the case for custom fields was inconsistent when retrieving the custom field.

✓