Multi-Factor Authentication - Code Not Working

In this article, we will guide you through initial triage steps for when your Multi-Factor Authentication (MFA) codes are not recognised upon attempting to sign into BigChange online.

If you wish to learn more about Multi-Factor Authentication (MFA), see What is MFA?

Initial Triage Steps

The affected web user(s) must have their Multi-Factor Authentication reset before attempting triage.

For instructions on how to reset Multi-Factor Authentication, see Resetting MFA for a Web User

Remove Multi-Factor Authentication from the web user on the BigChange site.
Delete any accounts on the Multi-Factor Authentication application that have been generated by BigChange when previously scanning the QR code.

We are not asking nor are you required to delete MFA for other sites or systems, as this only pertains to BigChange MFA accounts.

Sign into BigChange and set up MFA again by scanning the QR code via the Multi-Factor Authentication Application.
Either clear your browser's cache, site data and cookies for all time OR open a different browser which you do not use for BigChange.
Go to BigChange and sign in using your credentials.
Enter your Multi-Factor Authentication code.

These steps may help you resolve issues you are experiencing with Multi-Factor Authentication in relation to logging into BigChange.

If these steps have not resolved the behaviour and you are certain you have followed the steps correctly, please continue reading this article.

Reasons Why Multi-Factor Authentication Can Fail

Multi-factor authentication (MFA) can sometimes fail or be rejected for various reasons. Here are some common issues and potential solutions:

Incorrect Time Settings

Issue - Time-based One-Time Password (TOTP) codes, such as those generated by Google Authenticator, rely on the correct time being set on both the server and the client device.

Solution - Ensure that the time on your device is synchronized with an internet time server. Most smartphones have an option to set the time automatically.

Out-of-Sync Tokens

Issue - Hardware tokens or software tokens can sometimes become out-of-sync with the server.

Solution - Some systems allow you to re-sync the token. Check the documentation for your specific MFA provider.

Incorrect Codes

Issue - Entering the wrong code can happen due to typographical errors or reading the code incorrectly.

Solution - Double-check the code and ensure you are entering it within the valid time window.

Expired Codes

Issue - TOTP codes typically expire after 30 seconds. If you take too long to enter the code, it may no longer be valid.

Solution - Generate a new code and enter it promptly.

Network Issues

Issue - Some MFA methods, like SMS or push notifications, rely on network connectivity. Poor network conditions can delay or prevent the delivery of codes.

Solution - Ensure you have a stable internet connection or cellular signal.

App Issues

Issue - The MFA app itself might have bugs or issues.

Solution - Ensure the app is up-to-date. Restarting the app or your device can also help.

Browser or Device Issues

Issue - Sometimes, specific browsers or devices might have compatibility issues.

Solution - Try using a different browser or device to see if the issue persists.

Security Policies

Issue - Some organisations have strict security policies that might interfere with MFA.

Solution - Consult with your IT department to understand any specific security policies that might be affecting MFA.

Unable to resolve the MFA issue?

Please speak to your IT Administrator(s) or reach out to the Multi-Factor Authentication application's developer for further guidance.

Conclusion

By following the initial triage steps and understanding common issues, you can resolve most MFA-related problems when signing into BigChange. If issues persist, consult your IT Administrator or the MFA application's developer for further assistance.