settings: identity verification hangs indefinitely instead of showing error about authelia

[glime-ai]

Please note this response was created using generative AI leveraging previously available information from the repository. This information may be helpful however it is our strong recommendation that you carefully consider the information before blindly applying it.

---

The error you encountered, "the code didn't match any recorded code challenges," typically indicates a mismatch between the one-time code you entered and the codes stored or expected by the system. This can happen due to several reasons:

1. Time Synchronization Issues: If the device generating the one-time code (e.g., a smartphone running Google Authenticator) is not properly synchronized with the server time, the generated codes may consistently be out of sync.

2. Incorrect Code Entry: Double-check the code you entered to ensure there were no mistakes in transcription or timing (i.e., the code didn't expire).

3. Server or Backend Issues: There might be issues with how codes are being generated or stored on the server. This could be due to a configuration error or a problem with the server's time settings.

To troubleshoot and resolve this issue, you can try the following steps:

• Ensure Time Synchronization: Make sure that the time on your device (which generates the OTP) and the server are synchronized. Use a time synchronization service like NTP on both the server and your device.

• Check Server Logs: Look for any related errors in the server logs that might indicate what went wrong during the code verification process.

• Review Configuration Settings: Verify the configuration settings related to session elevation and OTP generation in Authelia. Ensure that they are set up correctly as per the documentation.

• Regenerate and Retry: Attempt to generate a new one-time code and use it promptly to avoid expiration issues.

If the problem persists, consider reaching out to the Authelia support community or checking the documentation for more detailed troubleshooting guides.

This comment was generated by Glime.

[stapelberg]

It’s clear to me now that authelia is generating another kind of one-time verification, sent via email, not a one-time password (TOTP).

I suggest changing the wording in the UI to make this more clear.

Regardless, the error should still be shown instead of silently swallowed :)

[james-d-elliott]

Thanks for the clear bug report, can confirm similar.

I suggest changing the wording in the UI to make this more clear.

What would you suggest changes with In order to perform this action policy enforcement requires additional identity verification and a One-Time Code has been sent to your email which is shown in the screenshot. How is it unclear that it was sent to your email?

[stapelberg]

Thanks for taking a look!

What would you suggest changes with In order to perform this action policy enforcement requires additional identity verification and a One-Time Code has been sent to your email which is shown in the screenshot. How is it unclear that it was sent to your email?

My suggestion is to change “a One-Time Code has been sent to your email” to “an Email Verification Code has been sent”, which is shorter and harder to misread.