21 December 2021 (v2.64)

ReachFive v2.64 focuses primarily on improving our Azure AD integration, enriching our Audit log module, and facilitating Multi-factor Authentication integration.

Integration

Azure AD connection

We’ve modified the configuration of Azure AD organizations to let you define a default role for user signin in the ReachFive Console. Previously, the default role was always CRM User.

We’ve also added a new role with no rights in the ReachFive Console if necessary for you.

For more information, check out our dedicated Azure AD guide .

Internationalization

We now support both Hungarian and Slovak languages accross the platform. Your end users will be able to see messages in these languages by using our SDKs or Hosted Pages.

Currently supported languages
Currently supported languages

  • ar - العربية Arabic

  • de - Deutsch German

  • en - English

  • es - Español Spanish

  • fr - Français French

  • hu - Magyar Hungarian

  • it - Italiano Italian

  • jp - 日本 Japanese

  • ko - 한국인 Korean

  • nl - Nederlands Dutch

  • pt - Portuguese

  • ru - Ру́сский Russian

  • sk - Slovenský Slovak

  • zh-CN - People’s Republic of China Simplified Chinese

  • zh-Hans - Simplified Chinese

  • zh-Hant - Traditional Chinese

  • zh-HK - Hong Kong Traditional Chinese

  • zh-MO - Macao Traditional Chinese

  • zh-SG - Singapore Simplified Chinese

  • zh-TW - Taiwan Traditional Chinese


Authentication

Facilitate the initiation of the stepup flow

You can now initiate a Multi-factor Authentication (MFA) stepup flow with an access_token.

We recommend that you only use this approach if you are unable to use the SSO session cookie or tkn approach.
For more details, check out our MFA Guide.


Security

Audit log module

We have improved our Audit log module to immediately detect job execution events.

For more information, check out our Audit logs page.


Fixes

Item Fixed

Vkontakte experienced a connection failure because of a modification in the API version.

✓

A user_updated event was generated at the end of a passwordless flow.

✓

The creation of a user with a created_at value in the past resulted in an error with the create user endpoint.

✓

The merge of two profiles containing only an external_id with the merge user endpoint resulted in an empty profile.

✓

The consent date could be updated when sending a payload that didn’t change the grant status of a consent.

✓