Quicken Multi-factor Authentication Process Enhancement
The MFA authentication process in Quicken is arduous enough without having to retype all the SMS codes received to authenticate. I submitted an enhancement for Quicken to auto populate the "ENTER CODE" after a MFA hs been requested via SMS.
This screenshot below displays the Quicken prompt for a MFA code and the incoming CODE received via SMS from WFB. The user needs to type the code into the Quicken prompt to complete the MFA script (for each MFA account being updated).
When logging into WFB Home Banking on Safari, going through the MFA process, Safari (or the Mac OS, not sure which) presents the code received via SMS as a possible entry "Fillcode #####." If the user selects the code from the Fill prompt, it automatically populates the "Code" prompt - WITHOUT HAVING TO RETYPE THE CODE.
Here's an example below. SELECT "Fill Code XXXX" and authentication continues.
This may not seem like a big deal but if you have multiple accounts using MFA, it takes a while to complete. This wouldn't help for those using MFA codes via email but I think most are using text messages.
QUICKEN ENGINEERING - GOT YOUR EARS ON? Anything to expedite the MFA process would help!
Comments
-
This is how it's supposed to work. Autofill of MFA codes worked just fine prior to macOS Ventura. For some reason, when running macOS Ventura, the autofill doesn't work, but when I ran macOS Monterrey it worked perfectly. There have been multiple users who have reported this (and Quicken Community Moderators even made a post saying it was a known issue at one point), but there hasn't been any headway on the issue. Hopefully Quicken Community moderators will see that users are still reporting this and forward it on through the proper channels.
0 -
Here are a couple of other threads detailing the same issue:
0 -
I just submitted this to Support. Kevin said he would move it along.
0 -
Verified - Case #10444187 - Quicken for Mac - SMS MFA Code not populating Autofill during account update (download) process.
The thing that disturbs me is it is being treated like a new case which, in fact, it is not. I'm going to call for more info and will keep updating until it's resolved.
In light of one post above that offers up the coding to allow "domain bound" autofill, I'm going to take another look at Safari's privacy settings. I have my system locked down pretty tightly and an using private relay which may have something to do with it (prevents IP address from being detected).
0 -
Had a 90 min call with Alex. Quicken acknowledges that, while SMS Autofill did work as designed in the past, it does not now. So, somewhere between the Ventura roll out and/or Quicken updates, functionality was lost. Quicken exhausted all efforts to resolve this case with no resolution so it has been internally closed (resolved is not an appropriate word).
0
