I apparently succeeded in setting up new login, including setting up two-factor ID.. I received this confirmation email "A multi-factor authentication (MFA) method has been enrolled for your Thrift Savings Plan account for...".
I used Chrome browser on Win 8.1 tablet (not the app).
However, when I return to TSP site to sign in, I'm still being prompted to set up new login. Here are the steps:
When I navigate to tsp.gov, I see regular "Log in" button and two banners at the top of the page... one has the "Set up new login" button, and the other refers to high traffic volumes (see screenshot, below). I close (X) both banners and click the regular "Log in" button. That opens the pop-up warning "You are entering a United States government information system..." When I click the "Acknowledge" button to close the pop-up, there's now only the "Set up new login" button. Has anyone else experienced this problem?
I'm guessing the server write a cookie once the user completes the new login process so it knows whether to display the regular "Login" button or the "Set up new login" button. I use the Cookie Keeper extension to manage which cookies are protected, so I'm guessing my browser deleted the new cookie before I realized it needed to be protected.
I'm concerned that starting over might cause other problem because the new login has already been set up on the server. Any thoughts?
I used Chrome browser on Win 8.1 tablet (not the app).
However, when I return to TSP site to sign in, I'm still being prompted to set up new login. Here are the steps:
When I navigate to tsp.gov, I see regular "Log in" button and two banners at the top of the page... one has the "Set up new login" button, and the other refers to high traffic volumes (see screenshot, below). I close (X) both banners and click the regular "Log in" button. That opens the pop-up warning "You are entering a United States government information system..." When I click the "Acknowledge" button to close the pop-up, there's now only the "Set up new login" button. Has anyone else experienced this problem?
I'm guessing the server write a cookie once the user completes the new login process so it knows whether to display the regular "Login" button or the "Set up new login" button. I use the Cookie Keeper extension to manage which cookies are protected, so I'm guessing my browser deleted the new cookie before I realized it needed to be protected.
I'm concerned that starting over might cause other problem because the new login has already been set up on the server. Any thoughts?