Client-side MFA - How To Enable Client-side MFA (for clients)

Introduction

This article guides clients through the necessary steps to prepare and enable Client-Side Multi-Factor Authentication (MFA) within Reward Gateway | Edenred (RGER). This feature allows RGER to recognize and trust the Multi-factor Authentication that your organization performs through your Identity Provider (IdP), such as Okta, Microsoft Azure, or Edenred Connect, minimizing additional MFA prompts when accessing RGER applications.

Outcomes

By following this guide, you will be able to:

• Ensure your Identity Provider is properly configured for MFA and Single Sign-On (SSO)
• Work with your Reward Gateway | Edenred contact to enable Client-side MFA
• Verify successful integration and a seamless sign-in experience on web and mobile platforms

Prerequisites

Before configuring Client-Side MFA, please ensure:

• Your organization uses Okta, Microsoft Azure, or Edenred Connect as your Identity Provider.
• MFA enforcement is enabled and active on your company's IdP.
• Single Sign-On (SSO) is configured on your platform and working successfully.
• You have liaised with your CSM or Reward Gateway | Edenred contact who will coordinate the configuration process.

Step-by-step Configuration Process

1. Confirm your MFA Identity Provider setup

Ensure your Identity Provider (Okta, Microsoft Azure, or Edenred Connect) has MFA enabled for users accessing your benefits platform.

2. Configure your Identity Provider to send the correct authentication context class reference (ACR) or authentication level claims in the SAML or OIDC tokens to Reward Gateway IdP

Ensure your IdP (Okta, Microsoft Azure, or Edenred Connect) has MFA enabled for users accessing Reward Gateway services. This signal informs Reward Gateway that the user has successfully completed MFA.  

Confirm that the claims in the token include MFA evidence (e.g., acr=urn:oasis:names:tc:SAML:2.0:ac:classes:MobileTwoFactorContract or equivalent).  

• For Okta:

Confirm in your Okta system logs or token introspection that the custom attribute used to pass MFA context is named auth_methods. This attribute indicates the MFA methods completed by the user. 

For more details, see the Okta Authentication Context documentation.  

• For Microsoft Azure:

Confirm in the SAML response that there is an attribute named authnmethodreferences or with the URL http://schemas.microsoft.com/claims/authnmethodsreferences which signals the MFA status. 

For additional information, refer to the Microsoft Entra ID SAML protocol documentation.

2. Verify SSO is functioning correctly

Test normal SSO works through your IdP without errors.

3. Discuss Client-Side MFA enablement with your Reward Gateway | Edenred contact

Request that the feature be enabled. Your contact with confirm when this has been set up.

4. After confirmation of enablement, conduct testing

Log in via your IdP with Client-side MFA enabled.

Confirm members are not prompted for a second MFA challenge when logging into the platform.

Perform the same test on mobile devices for the Engage app

5. Report any issues with MFA

If you experience unexpected MFA prompts or login difficulties, share any details with your CSM (or other Reward Gateway | Edenred contact) for troubleshooting.

Troubleshooting Tips

• If you still see multiple MFA prompts, ensure your IdP is passing the correct authentication context to Reward Gateway IdP.
• Your eward Gateway | Edenred contact may review internal logs to confirm whether MFA signals are correctly received.
• Confirm that mobile the appropriate SSO is enabled, if mobile experience is inconsistent.

Best Practices

• Maintain active communication with your Reward Gateway | Edenred contact throughout setup.
• Validate your existing SSO and MFA setup independently before enabling Client-Side MFA.
• Test thoroughly on all platforms your employees use (web and mobile).
• Contact support promptly if issues arise - this facilitates log review and quicker resolution.