nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Fidelity - reauthentication required when I switch Quicken databases

MSVA

I have two active Quicken databases—one for myself and another for some accounts I manage. When I switch from one database to the other, I have to reauthenticate the Fidelity accounts.

All of the Fidelity accounts in the two databases are accessed through the same user name and password. Until the recent Fidelity/Quicken change over, I could move seamlessly between the two accounts.

Now I have to reauthenticate the accounts in each database when I switch between them. Does anyone know why this is happening and whether it can be fixed?

I use Quicken Classic Business & Personal for Windows.

[Edited - Readability]

Find more posts tagged with

Investments

Online Banking

Windows

Comments

Quicken Kristina

Hello @MSVA,

Thank you for letting us know you're seeing this issue. Based on your description of the problem, it sounds like Fidelity is issuing just one authentication token, and authorizing the accounts in one Quicken file deauthorizes the accounts in your other Quicken file.

You mentioned that it's the same username/password. Is it also the same accounts connected in both files?

Have you contacted Fidelity about this issue?

I look forward to your response!

MSVA

The two Quicken files are connected to different Fidelity accounts, but all of the accounts share the same Fidelity login. Is a Fidelity authorization token specific to one Quicken file? How would Fidelity know? Or is Quicken storing the Fidelity authorization token in the data file? And what would have changed in the last few months?

Quicken Kristina

Thank you for your reply,

According to our article on Quicken connection types, a secure token is stored on our aggregation partner's servers.

I don't have anything in writing that specifies whether or not a token is associated with a specific Quicken file. However, based on behavior I've observed, it acts like each token is associated with a specific file.

Fidelity would know because the token is used in place of login credentials. If you're using a token they see as invalid/expired, you would get the reauthorization prompt in Quicken.

Have you contacted Fidelity about this issue?

Thank you!

MSVA

I figured it out. The secret is to authorize on Fidelity all accounts that I want to see for both files, and then in each file to tell Quicken to ignore the accounts that I don't want to download to that particular file.

NotACPA

https://community.quicken.com/discussion/comment/20537089#Comment_20537089

Useful advice. Thanks for chasing it down.

Quicken Kristina

Thank you for the follow-up,

I'm glad to hear you found a resolution, and thank you for sharing the solution you found!

Hopefully, it will help others encountering the same issue!