20 November 2025 (v2.146)

ReachFive v2.146 brings several new features:

In addition, we have a new UI SDK 1.39.0 release which includes several important enhancements.

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


Release highlight

International Consumer Experience (ICE)

ReachFive’s International Consumer Experience (ICE) feature empowers seamless profile management across multiple ReachFive accounts, allowing you to unify your user data across disparate systems with precision and efficiency. By syncing profiles between a Source account and a Target account, you can ensure consistent user experiences while adhering to regional data models and compliance requirements.

For instance, a global e-commerce platform operating in France and Korea can synchronize user profiles from its French Source account to its Korean Target account, mapping fields like language preferences or regional identifiers to maintain a cohesive customer journey. This reduces operational silos, streamlines data governance, and enhances personalization, all while leveraging ReachFive’s robust CIAM infrastructure to maintain security and scalability.

ice overview

For full details, see International Consumer Experience.


Identities object retrieved in Kakao signup

We now retrieve the Identities object when users sign up or log in using Kakao. This allows for better management of user identities and improves the overall authentication process.

For more details on this provider, see Kakao Connect.


UI SDK 1.39.0

We have introduced several improvements in the latest UI SDK release. This includes:

UI SDK improvements

  • The birthdate field in the signup form now lets you select the month and year directly from a dropdown menu, ensuring consistency for your users. Use min and max to enforce who is allowed to sign up, and yearRange to decide which years are actually selectable in the dropdown. Set yearRange wide enough to cover the same span that max allows; otherwise eligible users might pass validation but be unable to pick their birth year. These attributes are available on all date fields in the UI SDK and help you enforce age restrictions.

    • Source

    • Visual 

    client.showAuth({
...
    signupFields: [
      {
        key: 'birthdate', (1)
        min: 18, (1)
        max: 115, (1)
        yearRange: 116 (2)
      },
      ... // other signup fields
    ],
    ...
})
    1 Sets the minimum and maximum age for the user and the range of years available in the dropdown from the current year. If not set, defaults to 6 and 129 for the minimum and maximum age.

    If users attempt to sign up outside of the defined age range, they will see an error message indicating the valid age limits.
    2 Sets the range of years available in the dropdown from the current year. Pick a value that covers the maximum age you allow (for example, 116 years for a max of 115). If not set, defaults to 10.

    Year range dropdown:

    birthdate dropdown

    Min/Max set error message:

    birthdate dropdown error

  • You can also now override the default label for any language in the UI SDK by passing it through the i18n configuration option. This allows for greater customization and localization of the user interface. If undefined, it will fall back to the default label provided by the SDK.

    showAuth example
    client.showAuth({
    i18n: {
      "fr": {
        "rememberMe": "Garder ma session ouverte pour 3 jours", (1)
      }
      "en": {
        "rememberMe": "Keep my session opened for 3 days", (2)
      }
    },
    …​
})
    1 French label override. Defaults to "Se souvenir de moi" if not provided.
    2 English label override. Defaults to "Remember me" if not provided.

UI SDK fixes

  • The asterisk (*) indicating a consent was required wasn’t appearing as expected.


General improvements

  • We have improved the user experience in the ReachFive Console for Email templates and SMS templates by updating the tabs to be positioned vertically, allowing for easier navigation between different template types.

    2146 template vertical scroll

  • We have also brought our token revocation policy more in line with RFC 9700 Section 4.14.2.


Fixes

Item Fixed

In some cases, Social Login buttons weren’t appearing correctly on the Authentication hosted page.

✓

When importing user profile information, the MFA email enrolment wasn’t being accepted even with the Force data update from file activated.

✓

In some limited instances, users attempting to log in with B.connect following a Google Connect login would receive an error message and be unable to log in.

✓

ReachFive Console

Custom fields with underscores weren’t mapping correctly for International Consumer Experience integrations.

✓