Title: Invalid authentication token
Last modified: August 21, 2016

---

# Invalid authentication token

 *  Resolved [Noumaan Yaqoob](https://wordpress.org/support/users/noumaan/)
 * (@noumaan)
 * [12 years, 5 months ago](https://wordpress.org/support/topic/invalid-authentication-token/)
 * When I try to scan the QR code or enter the secret key manually in Google Authenticator
   App, I get the error The barcode ‘otpath://totp/SiteName?secret=XXXXXXXXXX’ is
   not a valid authentication token barcode. What could be wrong?
 * [http://wordpress.org/plugins/wp-google-authenticator/](http://wordpress.org/plugins/wp-google-authenticator/)

Viewing 6 replies - 1 through 6 (of 6 total)

 *  Plugin Author [julien731](https://wordpress.org/support/users/julien731/)
 * (@julien731)
 * [12 years, 4 months ago](https://wordpress.org/support/topic/invalid-authentication-token/#post-4384634)
 * I’ve never encountered this issue before.
 *  [djanem](https://wordpress.org/support/users/djanem/)
 * (@djanem)
 * [12 years, 4 months ago](https://wordpress.org/support/topic/invalid-authentication-token/#post-4384643)
 * I get the same thing. I had to deactivate the plug-in because I couldn’t get 
   it to work with my Google Authenticator app. I tried manually adding the key 
   as well and that didn’t work either.
 *  [jeremyawhite](https://wordpress.org/support/users/jeremyawhite/)
 * (@jeremyawhite)
 * [12 years, 3 months ago](https://wordpress.org/support/topic/invalid-authentication-token/#post-4384646)
 * The issue is probably a space in WP Google Authenticator Settings > Site Name.
   It isn’t encoded correctly in the current version. You can fix it by removing
   the space or waiting for the code to be fixed.
    I’ve written a fix and issued
   a pull request on GitHub, so it’s just a matter of Julien accepting it and updating
   the plugin.
 * Edit: This may only be an issue if you use Google Authenticator on iOS. An update
   to the app may fix it if the app gets more lenient in what it accepts.
 *  Plugin Author [julien731](https://wordpress.org/support/users/julien731/)
 * (@julien731)
 * [12 years, 3 months ago](https://wordpress.org/support/topic/invalid-authentication-token/#post-4384647)
 * Indeed jeremyawhite fixed the issue. I just updated the plugin and it should 
   be alright now.
 *  [the_wrong_alice](https://wordpress.org/support/users/the_wrong_alice/)
 * (@the_wrong_alice)
 * [12 years, 3 months ago](https://wordpress.org/support/topic/invalid-authentication-token/#post-4384648)
 * Could you tell me what the problem was? I’m trying to fix this problem in my 
   own app :/
 *  Plugin Author [julien731](https://wordpress.org/support/users/julien731/)
 * (@julien731)
 * [12 years, 3 months ago](https://wordpress.org/support/topic/invalid-authentication-token/#post-4384649)
 * Of course. You can refer to this GitHub pull request: [https://github.com/julien731/WP-Google-Authenticator/pull/4](https://github.com/julien731/WP-Google-Authenticator/pull/4)
 * You’ll see the code and jeremyawhite’s comments.

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Invalid authentication token’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/wp-google-authenticator_889bf3.svg)
 * [Authenticator for WordPress](https://wordpress.org/plugins/wp-google-authenticator/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-google-authenticator/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-google-authenticator/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-google-authenticator/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-google-authenticator/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-google-authenticator/reviews/)

 * 6 replies
 * 5 participants
 * Last reply from: [julien731](https://wordpress.org/support/users/julien731/)
 * Last activity: [12 years, 3 months ago](https://wordpress.org/support/topic/invalid-authentication-token/#post-4384649)
 * Status: resolved