?
avatar uglyeoin
uglyeoin
9 Mar 2016

Steps to reproduce the issue

2 Factor Authentication must be enabled. Every now and then it goes out of sync (or something goes wrong). At that point if you enter in a two factor authentication you get the error message:

An error has occurred must match character set with 2 factor authentication

To log in you must remove any characters from 2FA and just use your user/password.

You then need to set up 2FA again. Alternately you can delete the database entry and log in without that error message.

I can show you this issue on a live client site but it is hard to deliberately replicate.

Expected result

Log in. Or an sensible error message that helps me to understand the issue. Perhaps this is a sensible error message but I don't know what it means. If it means something to someone can you assist me as it might help me to avoid the issue happening in the future.

Actual result

It looks like it logs in, but nothing is available except this error message: An error has occurred must match character set with 2 factor authentication. You then have to click "back to login" or some similar button.

System information (as much as possible)

This is a long standing issue that I have had over multiple websites. I have spoken to my host in great length about it and they have tried to assist in many ways, I can provide that information if it is helpful. In any event I find the error message unhelpful.

avatar uglyeoin uglyeoin - open - 9 Mar 2016
avatar uglyeoin uglyeoin - change - 9 Mar 2016
The description was changed
avatar wilsonge
wilsonge - comment - 9 Mar 2016

This sounds like this issue #4126 which was basically related to when the secret key changes stuff blows up. Would this make sense?

avatar uglyeoin
uglyeoin - comment - 9 Mar 2016

@wilsonge it is possible that I backed up on a staging server and transferred across. That would explain the intermittent nature of the issue. Does the secret key change when you do a Joomla! update?

avatar brianteeman
brianteeman - comment - 9 Mar 2016

no

On 9 March 2016 at 14:47, uglyeoin notifications@github.com wrote:

@wilsonge https://github.com/wilsonge it is possible that I backed up
on a staging server and transferred across. I wouldn't say it's 100%
though. Does the secret key change when you do a Joomla! update?


Reply to this email directly or view it on GitHub
#9349 (comment).

Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/

avatar uglyeoin
uglyeoin - comment - 9 Mar 2016

@wilsonge @brianteeman in which case let's assume it is the same issue until I can say for sure that it is not.

avatar uglyeoin uglyeoin - change - 9 Mar 2016
Status New Closed
Closed_Date 0000-00-00 00:00:00 2016-03-09 15:24:05
Closed_By uglyeoin
avatar uglyeoin uglyeoin - close - 9 Mar 2016
avatar riker1701d
riker1701d - comment - 21 Oct 2016

I experienced this error after setting up a new instance.
No Akeeba backup involved. No backup/restore of any sort was involved.
The site just stopped allowing 2FA access.
It was just updated to Version 3.6.3 a couple of days ago. Could that have affected it?
I regained access by renaming the twofactorauth directory then disabling and re-enabling the plugin "Two Factor Authentication - Google Authenticator". I re-setup the 2FA for the user and it worked again.


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/9349.

avatar wilsonge
wilsonge - comment - 21 Oct 2016

That's this issue #12487

Please test this patch #12497

Add a Comment

Login with GitHub to post a comment