Yesterday I felt so good getting my new phone completely set up. Little did I know I had more to do. I discovered that today during a meeting. I tried to log into a secure system and it needed my multi-factor-authentication (MFA) token. While some of the services got configured with the data transfer, some of them did not and I didn't realize it.
I use Microsoft Authenticator for most of my MFA access. I also have RSA and Okta set up on my phone but have done a good job of focusing using a single tool. For some reason my work account has some level of extra security. Copying the data from my old phone didn't copy the necessary information for my work account. When I went to log into a secure data system this morning, I never received a message with the MFA token used to complete the login. All I could do in my meeting was explain I updated my phone and would have to get the necessary information after the call finished.
All I needed to do is log into Microsoft Authenticator. When it came time to receive the MFA token, I made sure to turn on the old phone first as it could receive the token or 2-digit number to use. After that little dance, I turned my old phone off again and have MFA tokens being sent to the new phone.
Not wanting to miss something else, I logged into my RSA and Okta apps on my new phone. Neither of them are set up at all. I will have to use my old phone to fix that for my new phone. Right now it is not an emergency and so I can wait a day or two. The trick is not waiting too long as I don't want to have to use the excuse that I updated my phone months ago and never got around to getting everything installed.
No comments:
Post a Comment