NoMethodError in Devise::DisplayqrController#update about devise_google_authenticator

[xntrik]

Hey @webhat - when I've had to generate new secret token values in the past, I would firstly disable your requirement for the token, then update the value. The current gem is actually 0.3.13, although, I think the following would still work for your version.

Open up rails console
u = User.find(id)
u.gauth_enabled = false
u.save

Double check you can login without the token.. then get back in the console.
u = User.find(id)
u.send(:assign_auth_secret)
u.save

Log back into the app, visit the /user/displayqr page, and they should have a new token
..

Let me know how that goes?

[webhat]

This works for me, and obviously this is not how a user would be able to update their token, an often overlooked use case is where a user changes phones and needs to re-activate their GA on this new device.

[xntrik]

Agreed.

I have a separate issue to allow users to cycle tokens on the displayqr
Page.

I'll try and get to that next.
On 28 Mar 2014 23:34, "Daniel W. Crompton" [email protected] wrote:

This works for me, and obviously this is not how a user would be able to
update their token, an often overlooked use case is where a user changes
phones and needs to re-activate their GA on this new device.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/21#issuecomment-38932517
.

[xntrik]

0.3.14 now has token refresh capability. Let me know if that's what you're after @webhat?

From the displayqr page, there's a button to update the secret token.

[webhat]

👍 Thanks, exactly what I want. I'll try it out and report back.

[xntrik]

I think this is all okay now - closing out.