121433-a-reminderwarning-about-2-step-verification-seed-code

== Content ==
			
If you use 2-step verification, I used Google Authenticator on Android, did you write down your "seed code"?
Its a code apparently generated by the app when you sign up for 2 Factor Authentication. I signed up so long ago that I have no recollection of ever seeing a code like that, but have been informed that I am probably just forgetting. I guess I didn't write mine down, which is unlike me since I tend to read the fine print and don't often miss these things.
 
If, like me, you don't have this seed code and your phone breaks, or is stolen or lost, you will be locked out of Wildstar.
You need to be able to access your google authenticator app to deactivate 2FA. If you don't have your phone anymore, you need the seed code generated when you first signed up for the app. If you didn't write that down, you need to contact customer support to get it deactivated for you. All this is written in the description of 2 step verification, almost leading you to believe the seed code is pointless since CS will remove it anyway.  What isn't written is the incredibly long support ticket response times that come along with this type of mistake. The fastest I've seen resolved was 24hrs with many still waiting 3 and 4 days for a CS response.
 
I'm not writing this to complain,  I get that I should have written down that code, I get that CS is busy fixing other shit and (hopefully) helping other people that are also paid subscribers. I'm just writing as a warning to those that haven't recorded their code anywhere.  You should be able to deactivate your 2FA while you have access to your phone, and reactivate to get a new seed code I think.
Better safe than sorry,	
----
			
To reiterate and summarize, make sure you have saved your seed code.  If you didn't, you can easily disengage your authenticator with your device.  Do this, then re-engage it with a new authenticator code, and make sure you have the seed code for that.
 
Also, I'd like to take the opportunity to remind Carbine and NCSoft that I'd gladly pay some extra money to get a Wildstar-ized VASCO token the way Square and Blizzard do.  That isn't subject to the same issue.	
----
			Is there any way to look up the seed code on the device I have the authenticator on, or at all, for that matter?	
----
			
not that I know of...from what I have read, its a one time thing. Write it down (not on your phone) when you sign up or lose it forever.
I could be wrong though.	
----
			
{| class="blockquote"
Is there any way to look up the seed code on the device I have the authenticator on, or at all, for that matter?
----
			
{| class="blockquote"
Is there any way to look up the seed code on the device I have the authenticator on, or at all, for that matter?
----
			
I  would like to add that if you did save your seed code and are getting an invalid code there may be 2 reasons for this to be happen.
 
1. Make sure your authentication app is time synced correctly. Go settings>Time correction for Codes>Sync Now
 
2. If time sync does not fix and you are 100% certain you put in the right code try using FreeOTP instead of google authenticate. There is known issue with google authenticate and android 4.4 kit kat where it will not give correct authenticator code.	
----
			
{| class="blockquote"
I  would like to add that if you did save your seed code and are getting an invalid code there may be 2 reasons for this to be happen.
 
1. Make sure your authentication app is time synced correctly. Go settings>Time correction for Codes>Sync Now
 
2. If time sync does not fix and you are 100% certain you put in the right code try using FreeOTP instead of google authenticate. There is known issue with google authenticate and android 4.4 kit kat where it will not give correct authenticator code.
----
			
{| class="blockquote"
No, short of possibly going through CS to get it. However, if you have the authenticating device, you can remove 2FA from your Wildstar account. Then, remove the Wildstar authenticator spinning on your device (in that order, don't remove that code cycle from your authenticator until you have removed 2FA from your account. Then set it up again just like the first time. It will give you a new seed code and your account will be protected with the new code (which you can write down). It's a relatively quick process (at least it was when I did it) and you don't need CS to do it. It's worth doing just in case your phone dies or you kill a piece of hardware.
----