26 June 2025 (v2.137)

ReachFive v2.137 is primarily a bug fixing release. However, we also improved a few items of note:

Fresh token no longer required for several endpoints
Adobe Campaign Classic available as an email provider

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

Fresh token no longer required for several endpoints

As part of our ongoing API improvements, the following endpoints no longer require a fresh access token. These endpoints accept either a fresh access token or an access token containing an amr claim that indicates multi-factor authentication (e.g., "amr": ["mfa"]). When an MFA-related amr claim is present, the system does not enforce token freshness.

This change simplifies API usage by reducing the need for repeated MFA prompts while maintaining security.

Email
Phone number
Other

Update email: /update-email
Verify email: /verify-email
Delete email MFA credential: /mfa/credentials/emails
Add email as second factor: /mfa/credentials/emails

Update phone number: /update-phone-number
Verify phone number: /verify-phone-number
Delete phone number MFA credential: /mfa/credentials/phone-numbers
Add phone number as second factor: /mfa/credentials/phone-numbers

Unlink social account: /unlink
List trusted devices: /mfa/trusteddevices
Delete trusted device: /mfa/trusteddevices/{deviceId}
Update password: /update-password

This update also applies to WebAuthn endpoints and Grants.

Adobe Campaign Classic

We now offer Adobe Campaign Classic as an email provider in the ReachFive Console.

You can configure Adobe Campaign Classic as an email provider in the ReachFive Console by going to Settings Email Providers. Then, select Adobe Campaign Standard/Classic from the list of available providers under Client type.

For more details, see Add Adobe Campaign Classic as an email provider.

General improvements

Now, when Data Breach Detection is enabled, the Suspend user option is disabled by default. This gives you the chance to customise your configuration before proceeding with the Data Breach Detection feature.
We have brought back the HTML? to the Update email template to ensure users can send HTML in the message if desired.

Fixes

Item	Fixed
MFA data wasn’t being retrieved properly in Webhooks and Pub/Sub hooks.	✓
In some instances related to MFA data, there were duplicate fields for Webhooks and Pub/Sub hooks.	✓
ReachFive Console
For a brief period, the users page on the needed to be manually refreshed to pick up changes.	✓
Some dialogs in the weren’t correctly applying dark mode .	✓
There were some minor fixes around label wording that were corrected.	✓
For a brief period, older user profiles weren’t being fetched properly.	✓

Item

Fixed

MFA data wasn’t being retrieved properly in Webhooks and Pub/Sub hooks.

✓

In some instances related to MFA data, there were duplicate fields for Webhooks and Pub/Sub hooks.

✓

ReachFive Console

For a brief period, the users page on the needed to be manually refreshed to pick up changes.

✓

Some dialogs in the weren’t correctly applying dark mode .

✓

There were some minor fixes around label wording that were corrected.

✓

For a brief period, older user profiles weren’t being fetched properly.

✓