I didn't save the token. Big oops or fixable? #237
Comments
|
Which token are you talking about specifically? You shouldn’t have to remember/record the six digit codes that the app generates. Every time you log into the account just use the code that is displayed on the app at that time. Some services give you backup codes that you can use if you can’t access your phone. You’ll want to write/print those somewhere. |
|
Hi,
The token on the Authenticator App. This is what happened…I took the photo of my computer screen to start the authentication process, the 6-digit code came up in the app, I typed it into my online account (which was accepted) and then I didn’t save it. By it, I mean the account information to the app (the app states to add a “token”…so I’m using that vernacular). Now, I don’t know how to get it back to access the six digit code. Does that make sense?
Also, I must offer apologies - I’m on a bit of a learning curve. I just figured out after sending the issue report that the code isn’t a one-time static thing. Anyway, I really just need to know if it’s possible to retrieve the account info/6-digit access code from the app. Right now, I open the app and there’s no record of any access code having been created.
Thanks very much for your help and patience!
Erin
… On Nov 17, 2017, at 11:10 AM, Robert “Beau” Collins ***@***.***> wrote:
Which token are you talking about specifically?
You shouldn’t have to remember/record the six digit codes that the app generates. Every time you log into the account just use the code that is displayed on the app at that time.
Some services give you backup codes that you can use if you can’t access your phone. You’ll want to write/print those somewhere.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#237 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AgLGDhE3kP4z9ugDYXKnyo7WnidPFedRks5s3b4egaJpZM4QhP6M>.
|
|
No worries Erin. Let's see what we can figure out. When you open the app is this what you see?
What you describe indicates that you successfully added the password generator to the app and it should have been saved. At any point did you hit a red "Delete" button? That should be the only way to delete the password generator from the app once you've gotten to the point where it displays a 6 digit code. If the app no longer has the password generator that you used to get the 6 digit code there is no way to recover it. You will have to remove two factor authentication on your account and start the setup process over. If you no longer have access to your account you will have to go through the website's account recovery steps. |
|
Yep…so blank. I fear the info fell into some dark vortex. Tell me it’s not so!
… On Nov 17, 2017, at 11:42 AM, Robert “Beau” Collins ***@***.***> wrote:
No worries Erin. Let's see what we can figure out.
When you open the app is this what you see?
<https://user-images.githubusercontent.com/19795/32960429-b12e5f1a-cb79-11e7-8c87-4d35a23e779b.jpeg>
What you describe indicates that you successfully added the password generator to the app and it should have been saved. At any point did you hit a red "Delete" button? That should be the only way to delete the password generator from the app once you've gotten to the point where it displays a 6 digit code.
If the app no longer has the password generator that you used to get the 6 digit code there is no way to recover it. You will have to remove two factor authentication on your account and start the setup process over.
If you no longer have access to your account you will have to go through the website's account recovery steps.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#237 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AgLGDhyZU6R9sZ4aVPpOI5Z7yF3hGBZLks5s3cWdgaJpZM4QhP6M>.
|
|
Yeah, unfortunately it seems to have fallen into this vortex you speak of. The curious thing is that once you've reached the point in the app that it shows you a 6 digit code it should at that point be saved and remain in the app until you delete it. At this point you need to disable/re-enable two factor on your account. |
|
Hmmm, it didn’t. This is vexing. But, I very much appreciate your help with my little conundrum.
Now, if you could deal with customer service for me, that would be fantastic. Ha.
Thanks!
Erin
… On Nov 17, 2017, at 11:59 AM, Robert “Beau” Collins ***@***.***> wrote:
Yeah, unfortunately it seems to have fallen into this vortex you speak of.
The curious thing is that once you've reached the point in the app that it shows you a 6 digit code it should at that point be saved and remain in the app until you delete it.
At this point you need to disable/re-enable two factor on your account.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#237 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AgLGDkbTywdDcvY42jjaXe0KZmWoBtYtks5s3clsgaJpZM4QhP6M>.
|
|
Hi,
I used this e-mail once before when I was having some technical issues. You were so helpful, I thought I try again in the hopes you might indulge my quest for understanding how this thing works.
If I save the Authenticator App with all of my “transactions” (for lack of a better word) to my computer and/or iCloud (with the encryption on), I can still always recover it even if I lose my iphone. Is that right? Or, is there something else I need to do to ensure I can still access my codes in the event of a lost phone?
I’m just making sure - crossing my t’s, if you will - before I go for round 2.
Many thanks and happy new year!
Erin
|
|
@Luddite88 you're mostly correct but I need to make one thing clear. The "Encrypt iPhone backup" option in iTunes only applies to backups stored on the computer, not in iCloud. Your Authenticator's secret codes are never stored in iCloud so restoring from an iCloud backup will never restore your secret codes. If you want to be absolutely certain that you have backed up your Authenticator codes:
Once this is completed you will have backed up Authenticator's secrets as they are at that moment in time. If you plug in a different phone and click "Restore Backup ..." and choose the encrypted backup you just made, the device will have the Authenticator app and the secret codes restored. |
|
Brilliant! You are a god among men...thanks for taking the time to explain in such detail..
Erin
…Sent from my iPhone
On Jan 5, 2018, at 11:32 AM, Robert “Beau” Collins ***@***.***> wrote:
@Luddite88 you're mostly correct but I need to make one thing clear.
The "Encrypt iPhone backup" option in iTunes only applies to backups stored on the compter, not in iCloud. Your Authenticator's secret codes are never stored in iCloud so restoring from an iCloud backup will never restore your secret codes.
If you want to be absolutely certain that you have backed up your Authenticator codes:
Open iTunes and go your phone's "Summary"
In the "Backups" section make sure the "Encrypt iPhone backup" checkbox is checked. If not, then check it and enter a password to use for encryption.
Under the "Manually Back Up and Restore" section of "Backus" click "Back Up Now"
Once this is completed you will have backed up Authenticator's secrets as they are at that moment in time.
If you plug in a different phone and click "Restore Backup ..." and choose the encrypted backup you just made, the device will have the Authenticator app and the secret codes restored.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Hi Matt,
I didn't save the token when I used the 6-digit code I was given. And, I didn't write down the code either. Is there a way to find it or a floating token (she says with wry smile) somewhere in the recesses of my phone? I can't access my account without a numeric code. Any guidance you can give this beginner (seriously, my first attempt at this crazy business of authenticating) would be most appreciated. Many thanks.
The text was updated successfully, but these errors were encountered: