25 June 2026 (v2.160)

Staging ๐Ÿงช

ReachFive v2.160 brings a few new features and updates:

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


Display richer details under user Recent Activity

In the ReachFive Console, you can now see richer details under a user’s Recent Activity. This includes details such as the user’s IP address, the involved ReachFive client, scope, and more.

When creating or editing a recent activity filter, you can set the filter to show the full details by default if desired.

For more details on this topic, see Managing users from the ReachFive Console.

  • View individual event details

  • View all event details

To view more details on an individual event:

  1. Go to Analytics  Profiles.

  2. Click your desired user.

  3. Go to the Recent activity tab.

  4. On your desired event, click Show more to see the details.

    user recent activity showMore

You can see details for all events by enabling the new Show all details toggle.

  1. Go to Analytics  Profiles.

  2. Click your desired user.

  3. Go to the Recent activity tab.

  4. Enable the new Show all details toggle to see details for all events.

    user recent activity



Store birthdate without a year

In some cases, you may need to store a user’s birthdate without a year for compliance or other reasons.

To do this, you can now set the birthdate user profile field to 0000-DD-MM. By setting the year to 0000, the year will be omitted from the birthdate when retrieving the user profile.

{
  "id": "550e8400-e29b-41d4-a716-446655440000",
  "name": "John Doe",
  "given_name": "John",
  "family_name": "Doe",
  "auth_types": [
    "password",
    "phone_number_password"
  ],
  "birthdate": "0000-01-01" (1)
}
1 In this example, the year is omitted from the birthdate.



Improved fields precedence logic for Managed and Lite profiles

We have updated the synchronization logic for fields between Managed and Lite profiles. Now, any changes made to a standard or custom field within a Managed profile automatically propagates to the corresponding Lite profile to ensure data consistency.

Importantly, this update prevents legacy Lite profile fields from repopulating a Managed profile once the user has transitioned to a managed state, ensuring your managed user data remains the single source of truth.

The feature must be enabled on your account by your ReachFive representative to take effect.

For more on this topic, see User profiles in ReachFive.

Diagram showing the flow of field updates between Managed and Lite profiles.



General improvements

  • Now if you change your custom domain, access tokens continue to work as expected.



Fixes

Item Fixed

In some limited instances, a password_reset_requested user event was being emitted inadvertently during a Risk-based Authentication flow.

During the /oauth/par and /oauth/authorize flow, some integrators were receiving a 400 error response instead of redirecting the user.

R5 AI Assistant

Confirm Deletion