31 July 2025 (v2.139)
ReachFive v2.139 introduces a couple of improvements and needed bug fixes.
We also have a new iOS SDK release where several enhancements have been made including breaking changes related to how futures are handled.
As always, we made some general improvements and fixed a few items for you.
Third-party grants visible in ReachFive Console
We have made third-party grants visible in the ReachFive Console to improve transparency and user awareness.
You can see the third-party grants in the Third-party consents tab of a user profile by going to .
Improved Data Breach Detection messaging
When a user’s credentials are detected as leaked by our Data Breach Detection scanning job, the ReachFive Console now displays more specific messages to ensure you understand what happened.
These messages appear in the Recent Activity section of the user profile.
Name included in reCAPTCHA configuration
We have added the name of the reCAPTCHA configuration to the ReachFive Console to make it easier to identify which configuration is being used.
The name is in brackets (parentheses) next to the Client ID.
General improvements
-
In some cases, MFA is required to access certain accounts on the ReachFive Console. We now provide clearer information to a user if MFA is required and they do not have MFA on their console account.
Fixes
| Item | Fixed |
|---|---|
There was a temporary issue where users were being redirected inadvertently to the ReachFive Console instead of the Microsoft Portal when authenticating with Entra ID (formerly Azure AD). |
✓ |
In some limited cases when a user trusted a device, the device was being registered multiple times, leading to duplicate entries in the trusted device list. |
✓ |
We removed an unnecessary scope for Listing trusted devices. |
✓ |
Google login was temporarily not working for native mobile SDKs. |
✓ |
ReachFive Console |
|
For a brief period, you were unable to delete a CaptchaFox configuration in the ReachFive Console. |
✓ |