24 October 2024 (v2.122)

ReachFive v2.122 introduces a few improvements and needed bug fixes. This includes being able to view MFA credentials in a user profile card. You can also now use multiple social provider accounts for select social providers and filter by social provider ID.

As always, we fixed a few items for you.


MFA credentials in user profile card

If enabled and present for an account, MFA credentials are now displayed on the user profile card in the ReachFive Console. An MFA credential is a mobile or email that the user has verified for use as a second factor for our MFA feature.

For more on these topics, see Multi-factor Authentication and Managing users from the ReachFive Console respectively.

2122 MFA profile


Use multiple social accounts for ReachFive account

You can now use multiple social accounts for your ReachFive account by providing a provider_variant when configuring the social account in the ReachFive Console.

This update applies to Facebook, Google, and Apple social login accounts.

To have a different "variant" of the social login, you’ll add a variant tab in the social configuration where you provide the client_id and client_secret needed for that particular account, allowing you to have multiple associated with your ReachFive account.

For more on this topic, see Meta Connect (Facebook Login), Sign in with Apple, and Google Connect respectively.

  • Apple

  • Facebook

  • Google

You must create a variant for Sign in with Apple now unless you use webviewLogin for all authentication flows, including Sign in with Apple (SiWA).

It’s important to note that the ReachFive Client ID mapping differs depending if you’re creating a connection for web context or native app context.

The text ios must be in the name of the variant.

add apple variant

Adding a variant with Meta Connect (Facebook Login):

2122 provider variant facebook

Adding a variant with Google Connect:

add google variant


Filter by social provider ID

You can now filter by the social provider ID (identities.id) on the /api/v2/users search users endpoint. This is useful in cases where a user has unlinked his or her profile from their social provider and you need to also unlink it from your brand’s side.

For more on this topic, see Identities object.

Example call
GET /api/v2/users?filter=identities.id=="kakaotalk:4211574058"


Fixes

Item Fixed

There was briefly an issue with retrieving custom fields when attempting to login as a user.

✓