What if I accidently delete my GLBSE account from Google Authenticator

vandordeak

newbie

Activity: 58

Merit: 0

Quote from: John (John K.) on July 18, 2012, 10:05:21 PM

Quote from: vandordeak on July 18, 2012, 06:16:13 PM

Quote from: John (John K.) on July 15, 2012, 09:02:10 PM

Quote from: vandordeak on July 15, 2012, 08:14:32 PM

I just set up Google Authenticator on my mobile. I got the following text when I want to delete my GLBSE account merged.

"Removing this account will remove your ability to generate codes, however it will not turn off 2-factor authenticitation. This may prevent you from signing into your account.

Before removing:

- Turn off 2-factor authenticitation for this account, or
- Ensure that you have an alternative mechanism for generating codes."

Can you tell me what are the possible alternatives avaliable? Just for experiment I tried to sign in with the backup keys from my google account, but did not work. I do not want to delete my merged glbse account from my android by mistake. I like my Glbse account too much to loose it. A new account wouldn't be the same

Back up the GA QR codes. I wondered about this issue last time too. You can have a fresh QR code by disabling GA and re-enabling GA again.

Just to make it clear.
If I back up the GA QR code, then if I loose my phone all I got to do is install GA on my new phone and use the back up codes to set up an account to get the proper one time password. Also disable the lost phone on my google account, and change password as soon as I can. Right?

If you lose your phone, install GA on your new phone, use the back-uped QR code to login, generate a NEW QR code and change the GA of your new phone to that new QR code. Doing this will revent the old QR code from being functional. lso disable the lost phone on your google account, and change password as soon as you can.

Thanks, thats makes sense.

John (John K.)

legendary

Activity: 1288

Merit: 1227

Away on an extended break

Quote from: vandordeak on July 18, 2012, 06:16:13 PM

Quote from: John (John K.) on July 15, 2012, 09:02:10 PM

Quote from: vandordeak on July 15, 2012, 08:14:32 PM

I just set up Google Authenticator on my mobile. I got the following text when I want to delete my GLBSE account merged.

"Removing this account will remove your ability to generate codes, however it will not turn off 2-factor authenticitation. This may prevent you from signing into your account.

Before removing:

- Turn off 2-factor authenticitation for this account, or
- Ensure that you have an alternative mechanism for generating codes."

Can you tell me what are the possible alternatives avaliable? Just for experiment I tried to sign in with the backup keys from my google account, but did not work. I do not want to delete my merged glbse account from my android by mistake. I like my Glbse account too much to loose it. A new account wouldn't be the same

Back up the GA QR codes. I wondered about this issue last time too. You can have a fresh QR code by disabling GA and re-enabling GA again.

Just to make it clear.
If I back up the GA QR code, then if I loose my phone all I got to do is install GA on my new phone and use the back up codes to set up an account to get the proper one time password. Also disable the lost phone on my google account, and change password as soon as I can. Right?

If you lose your phone, install GA on your new phone, use the back-uped QR code to login, generate a NEW QR code and change the GA of your new phone to that new QR code. Doing this will revent the old QR code from being functional. lso disable the lost phone on your google account, and change password as soon as you can.

vandordeak

newbie

Activity: 58

Merit: 0

Quote from: John (John K.) on July 15, 2012, 09:02:10 PM

Quote from: vandordeak on July 15, 2012, 08:14:32 PM

I just set up Google Authenticator on my mobile. I got the following text when I want to delete my GLBSE account merged.

"Removing this account will remove your ability to generate codes, however it will not turn off 2-factor authenticitation. This may prevent you from signing into your account.

Before removing:

- Turn off 2-factor authenticitation for this account, or
- Ensure that you have an alternative mechanism for generating codes."

Can you tell me what are the possible alternatives avaliable? Just for experiment I tried to sign in with the backup keys from my google account, but did not work. I do not want to delete my merged glbse account from my android by mistake. I like my Glbse account too much to loose it. A new account wouldn't be the same

Back up the GA QR codes. I wondered about this issue last time too. You can have a fresh QR code by disabling GA and re-enabling GA again.

Just to make it clear.
If I back up the GA QR code, then if I loose my phone all I got to do is install GA on my new phone and use the back up codes to set up an account to get the proper one time password. Also disable the lost phone on my google account, and change password as soon as I can. Right?

RandomQ

hero member

Activity: 826

Merit: 500

Quote from: Bitcoin Oz on July 15, 2012, 09:24:16 PM

I discovered if you already have an account setup with GA and then try to scan the qr code for new account it overrides your first account and replaces it with the new one meaning your old account will still have GA but no way to use it.

I think that is an android issue, because I have 2 google OTP GLBSE accounts and 2 Google OTP MTGOX accounts on IOS currently working correctly

I've emailed glbse in the past because of a problem with an account losing google OTP access(reinstalled OS on phone and google OTP didn't backup correctly)

My 3rd account that I can login too but not transfer or withdraw without correctly.

5/13/2012
Hi ***********
we can't disable twofactor once it's been enabled.

GLBSE support.

> Hi,
> I need to either disable the two-factor or transfer all assets to my
> new account (GreenBTC)
>

Bitcoin Oz

hero member

Activity: 686

Merit: 500

Wat

I discovered if you already have an account setup with GA and then try to scan the qr code for new account it overrides your first account and replaces it with the new one meaning your old account will still have GA but no way to use it.

John (John K.)

legendary

Activity: 1288

Merit: 1227

Away on an extended break

Quote from: vandordeak on July 15, 2012, 08:14:32 PM

I just set up Google Authenticator on my mobile. I got the following text when I want to delete my GLBSE account merged.

"Removing this account will remove your ability to generate codes, however it will not turn off 2-factor authenticitation. This may prevent you from signing into your account.

Before removing:

- Turn off 2-factor authenticitation for this account, or
- Ensure that you have an alternative mechanism for generating codes."

Can you tell me what are the possible alternatives avaliable? Just for experiment I tried to sign in with the backup keys from my google account, but did not work. I do not want to delete my merged glbse account from my android by mistake. I like my Glbse account too much to loose it. A new account wouldn't be the same

Back up the GA QR codes. I wondered about this issue last time too. You can have a fresh QR code by disabling GA and re-enabling GA again.

vandordeak

newbie

Activity: 58

Merit: 0

I just set up Google Authenticator on my mobile. I got the following text when I want to delete my GLBSE account merged.

"Removing this account will remove your ability to generate codes, however it will not turn off 2-factor authenticitation. This may prevent you from signing into your account.

Before removing:

- Turn off 2-factor authenticitation for this account, or
- Ensure that you have an alternative mechanism for generating codes."

Can you tell me what are the possible alternatives avaliable? Just for experiment I tried to sign in with the backup keys from my google account, but did not work. I do not want to delete my merged glbse account from my android by mistake. I like my Glbse account too much to loose it. A new account wouldn't be the same

Topic: What if I accidently delete my GLBSE account from Google Authenticator (Read 2768 times)