Is Keychain needed to update Quicken Mac?

R Strax
R Strax Member ✭✭✭✭
I do not use keychain on my Mac for passwords. I use another password manager. When I try to download transactions from my bank (Chase) I not only need to go through Quicken's multi factor authentication screens (which seem to take a long time, about 4-5 minutes), but Quicken repeatedly makes me log back into my account. It always asks if I want to add the password to Keychain, which is deactivated on my Mac. I wonder if not using Keychain is somehow preventing Quicken from logging in to my account quickly?

Answers

  • R Strax
    R Strax Member ✭✭✭✭
    edited January 2022
    Thanks! Since I cross platforms I use an independent PW manager (1Password) and have Keychain disabled so they won't compete in filling logons.

    How can I activate Keychain just for Quicken but not have it try to fill passwords elsewhere? Am I just doomed to prolonged account downloads and filling my info over and over? Is there any way that Quicken can use my independent PW manager to access my accounts?
  • R Strax
    R Strax Member ✭✭✭✭
    I would be willing to put up with two competing password fillers. My problem with using both 1Password and Keychain is synchronizing the passwords for different sites. One of them would always be out of date.
  • R Strax
    R Strax Member ✭✭✭✭
    edited January 2022
    RickO said:

    How did you actually disable the keychain? 


    Go to Settings > Passwords > AutoFill > Uncheck Keychain
  • R Strax
    R Strax Member ✭✭✭✭
    That’s correct on the Mac. I was looking at my iPhone. 
  • R Strax
    R Strax Member ✭✭✭✭
    Thanks. I’m still wrestling with Quicken making me log into the bank every time I download transactions.
  • Jon
    Jon Quicken Mac Subscription SuperUser, Mac Beta Beta
    edited January 2022
    You might want to check your keychain & make sure the passwords are actually getting stored. In the  Keychain Access app, look at the login keychain & you should see a bunch of entries that look like "Quicken password for customer X at Y", where X is your username at bank Y. If you don't see any entries like that, it would mean that something is preventing Quicken from storing passwords in the keychain. I don't know what would do that; I would suggest contacting Quicken customer service at that point.

    R Strax said:
    My problem with using both 1Password and Keychain is synchronizing the passwords for different sites. One of them would always be out of date.
    That's going to be an issue anyway. Since Quicken uses its own unique set of keychain entries, when you change a password you're going to have to update it twice - once in your web browser password manager, and once in Quicken. Even if you used the keychain instead of 1Password you would still have to do that.
  • R Strax
    R Strax Member ✭✭✭✭
    I have re-activated Keychain on my Mac. However, I am still confronted with a Quicken window requiring me to log in to my Chase bank account every time I update (even though this info was entered when I set up my account). The window always asks if I want to save this to Keychain, and I check the box "yes". However Quicken does not seem to remember my logon info. This is becoming very time consuming and annoying. Is this a known bug? I haven't seen it from anyone else, so I am wondering if there is something I can do to get Quicken to remember my bank log in info. This just started about 3-4 months ago, and the only changes have been Quicken updates as they have come along.

    Thanking you in advance!
  • R Strax
    R Strax Member ✭✭✭✭

    I might add that when I go to "Keychain Access" the passwords are present under "Quicken password for customer (logon ID) at Chase". So I wonder what I can do to get Quicken to access these passwords?
  • R Strax
    R Strax Member ✭✭✭✭
    All the Quicken password entries are in the "Login" tab.
    I will try to disconnect, delete password entries for accounts from that bank, and then reconnect. 

    I'll let you know how it goes. Thank you so much for your help!
This discussion has been closed.