WordPress.org

Forums

Google Authenticator
[resolved] Scanning barcode doesn't work (19 posts)

  1. Rob Roy
    Member
    Posted 2 years ago #

    The barcode 'otpauth://totp/MerwellEngine?secret=FAKESECRETKEY' is not a valid authentication token barcode.

    Try Again

    http://wordpress.org/extend/plugins/google-authenticator/

  2. Henrik Schack
    Member
    Plugin Author

    Posted 2 years ago #

    What are you talking about ?

  3. Rob Roy
    Member
    Posted 2 years ago #

    In the wordpress backend, the barcode generated to configure authenticator doesn't work. Scanning it give the error above

  4. Henrik Schack
    Member
    Plugin Author

    Posted 2 years ago #

    Thats strange, are you using an iPhone ?
    I known iPhones dont like descriptions containing spaces.

    Best regards
    Henrik Schack

  5. Rob Roy
    Member
    Posted 2 years ago #

    Yeah, I'm scanning the barcode with an iPhone.

  6. Henrik Schack
    Member
    Plugin Author

    Posted 2 years ago #

    Hmm something in the description must upset your iPhone, not sure what it is, I use Android myself.

    You could enter the secret manually ?

    Best regards
    Henrik Schack

  7. Henrik Schack
    Member
    Plugin Author

    Posted 2 years ago #

    Hi
    Did you manage to get it working ?

    Best regards
    Henrik Schack

  8. Henrik Schack
    Member
    Plugin Author

    Posted 2 years ago #

    No response, closing issue

  9. SemperFideles
    Member
    Posted 2 years ago #

    I'm having this issue as well. When I try to scan the barcode it says "Invalid Barcode...not a valid authentication token barcode.

    I am using an iPhone and I've set up multiple other apps with Google Authenticator.

  10. SemperFideles
    Member
    Posted 2 years ago #

    I figured it out. If there is a space in the Name of the Site (i.e. My Blog) then it fails but if you type without space (i.e. MyBlog) then the code goes through.

  11. Henrik Schack
    Member
    Plugin Author

    Posted 2 years ago #

    Yes, it is mentioned in the FAQ, would be nice if the Android and iPhone app would agree on what's possible :-)

    http://wordpress.org/extend/plugins/google-authenticator/faq/

    Best regards
    Henrik Schack

  12. SemperFideles
    Member
    Posted 2 years ago #

    One of the ways you can avoid users reporting this is that your plugin actually creates a default site name that has a space in it. If you remove the space in your code then you won't have lazy people like me who don't notice the FAQ. Also, you could put some instructions next to the field entry that instructs the user to use no spaces.

    Just a friendly suggestion. Great plugin.

  13. Henrik Schack
    Member
    Plugin Author

    Posted 2 years ago #

    I think I'll follow your suggestion and change the default :-)
    Thanks

    Best regards
    Henrik Schack

  14. Rob Roy
    Member
    Posted 2 years ago #

    Is that entry field available to all users or just the Administrator?

  15. Henrik Schack
    Member
    Plugin Author

    Posted 2 years ago #

    It' available to all users, unless disabled by an administrator.

    Best regards
    Henrik Schack

  16. Sean Donovan
    Member
    Posted 2 years ago #

    Where do you change the default "Name of Site" for the GA plugin? I would say this is a critical bug and agree strongly with @SemperFideles.

  17. Henrik Schack
    Member
    Plugin Author

    Posted 2 years ago #

    Hi Sean Donovan
    As mentioned, I'll change the default, that will happpen the next time I release an update.
    This will probably solve this "critical bug" for you and SemperFideles, but new critical bugs will be created by people still creating descriptions containing spaces and using an iPhone.
    Then I could silently remove any entered space characters before creating the QR code, and people would start complaining about that.

    The right way to solve this issue, is to have it fixed at the root.
    Google created the Google Authenticator App for IOS and Android, Google created the app in way that it behaves differently depending on if you're using an iPhone or an Android phone.

    Best regards
    Henrik Schack

  18. Sean Donovan
    Member
    Posted 2 years ago #

    Thanks for the lengthy report. I agree -> I should probably google to see if there is a bug reporting interface for the iPhone authenticator app.

  19. SemperFideles
    Member
    Posted 2 years ago #

    Henrik,

    Appreciate the work. Not a critical bug for me. All I needed to know was to make sure I didn't put a space in the Site Name and I was good to go. I really appreciate the app.

    My suggestion was aimed at primarily saving you the grief of people constantly telling you about the problem. A couple of things you could do:

    1. Change the default name that is generated during the plugin install. I didn't change the name because I'm lazy and am like a majority of users who leave the default value. You'll then eliminate a good number of problems.

    2. Place instructions underneath the site name that explicitly warns the user that if they use a site name with a space in it that it's not going to work on the iPhone.

    These two steps ought to be fix enough to keep you getting a steady stream of complaints.

Topic Closed

This topic has been closed to new replies.

About this Plugin

  • Google Authenticator
  • Frequently Asked Questions
  • Support Threads
  • Reviews

About this Topic

Tags

No tags yet.