Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Google Authenticator was unable to read the code #11

Open
pcdog opened this issue Jan 27, 2017 · 9 comments
Open

Google Authenticator was unable to read the code #11

pcdog opened this issue Jan 27, 2017 · 9 comments

Comments

@pcdog
Copy link

pcdog commented Jan 27, 2017

one of my users got the error message from Google Authenticator that "Is unable to interpret this code"

In German, it was "Code kann nicht ausgewertet werden"

My WHMCS version is the newest 7.1

entering the code from hand worked

@wzul
Copy link
Contributor

wzul commented Jan 27, 2017

I don't face the issue. Btw, I have update the Google Authenticator class with the latest one. Don't know if this have an effect on this issue or not. I have upload it to my repo too! :)

@dionysius
Copy link
Contributor

@wzul can you open a pull request please
@pcdog can you somehow make a screenshot of that image so I can investigate?

@pcdog
Copy link
Author

pcdog commented Jan 28, 2017

Will do, need the colleague back in the office tomorrow ;)

@wzul
Copy link
Contributor

wzul commented Jan 28, 2017

@dionysius will do. But,

  • I change every code for database query to use Capsule (sometimes even we don't need to).
  • I change the flow if the client login using Backup Code. The client will be given new Backup Code instead disabling the Two-Factor.

Is that ok? I am new to git. Teach me please :)

@dionysius
Copy link
Contributor

@wzul then it is difficult :) no problemo, I'll have a look myself

@jozephbrasil
Copy link
Contributor

@wzul send us the code then we can PR the code. There is instructions on github that help make this easier. I am on phone now and as soon as possible I will send you links with help. Basically you need to fork and and send a PR after changes.

@wzul
Copy link
Contributor

wzul commented Jan 28, 2017

@dionysius @jozephbrasil

Sorry for late. You have found my code and it was sent to pull request.

Thank you :)

@dionysius
Copy link
Contributor

I've merged the pull request of wzul so you might test it when I release the next version. If it fails: please provide (e.g. from a dummy account for privacy reasons) a screenshot of the qr-code

@dionysius dionysius removed their assignment Apr 15, 2017
@007basaran
Copy link

007basaran commented Oct 31, 2017

Hello,

Go whmcs module folder.

/htdocs/modules/addons/oath

Open the clientareaoath.tpl with notepad++

Find This Line : <img src="{$modulelink}&qr=1&secret={$secret}" />

Change TO : <img width="177" height="177" src="{$modulelink}&qr=1&secret={$secret}" />

Return oauth page and CTRL + F5 flush page. Authenticator will work this time.

Regards.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants