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; } } }

Multiple data files clash over Fidelity account tokens

AZ66

Using Quicken Classic Deluxe R65.17 on a Windows 11 machine. I have multiple Quicken data files to keep things separate. Across those multiple files I keep getting requested to reset or verify my Fidelity accounts almost every time after I Update. They have been doing this for months now, but only after a lot of experimentation have I determined the core issue.

If I update Data File A and correctly authenticate the details with Fidelity it will work fine until I then go to Data File B and then I can't update that one without authentication. Clearly the issue is that the authentication approval token(s) are being stored on my computer and apply to ALL the data files, but that isn't correct. Those tokens should apply to only the specific data file. Please fix this as it makes Quicken update unusable at this time and if this continues I will have to migrate to another platform after 25+ years. (see also the related post below). @Quicken Kristina

https://community.quicken.com/discussion/comment/20513391#Comment_20513391

Find more posts tagged with

Online Banking

Windows

Data File

Comments

AZ66

Here's some further info after a bit more testing today. I accidentally did the following:
- Opened Data File B and got the error saying that my Fidelity accounts were not properly linked. However when I tried to Reset and the Fidelity login page on my browser opened, I accidentally closed the Fidelity login page and so had to cancel the reset. I then re-ran the Update and it appeared to work ok (no error generated). I re-ran the Update several times more with no error generated. I'm not sure if that will always be the case, but maybe this info helps.

Quicken Kristina

Hello @AZ66,

Thank you for sharing your experience. Typically, if multiple Quicken files are fighting over the same token, it is due to a financial institution limitation. It is interesting that starting, but not finishing the reauthorization seemed to work.

Thank you!

AZ66

Thanks @Quicken Kristina. Ok, but this only started when Quicken made the change to how it handled money market / cash in Fidelity accounts a few months ago. Since then I have been having all types of issues with the Fidelity accounts. There are clearly still bugs in the software that need to be worked out.

Boatnmaniac

Are you using the same Fidelity login for both files?

If so, when you authorize Fidelity for the 1st file, are you selecting all available accounts for downloading…even those that you do not want downloaded into that file?

If not, you might want to try doing that. Then when you are prompted to decide what to do with the downloaded data, be sure to LINK the accounts to those that are already in the data file and select DO NOT ADD for the accounts that you do not want added.

For the 2nd file, follow the same process (of course, changing which accounts are to be LINKED and which ones are to not be added).

I have done this in the past with Fidelity Investments (EWC+ connection) and it then allowed the token to work with both files and I was no longer prompted to reauthorize each time I switched between the files. It is the data file, then that determines which accounts are to be downloaded into each file while leaving the reauthorization token intact and unaffected.

Maybe that will work for you, too?

AZ66

Thanks @Boatnmaniac! That suggestion seems to have addressed the issue (at least after some very limited testing). So the key is the approve EVERY account in the Fidelity system that one wants to sync in ANY Quicken file. Then choose which accounts to sync in each Quicken file. Not very intuitive in my opinion, but I get it now.

Boatnmaniac

https://community.quicken.com/discussion/comment/20525138#Comment_20525138

I'm glad to hear it is working for you. Yes, not very intuitive. Unfortunately, it seems there is not a consistent token management protocol used by all financial institutions, especially when there are multiple data files involved or when there are multiple logins involved. If there were a consistent protocol it would make it a whole lot easier but I'm guessing each financial institution wants to manage their security in the way they think is best.

In Fidelity's case, it seems they issue one security token per Quicken ID instead of per data file ID or Cloud Account ID. Just a guess but it seems like that might be the case.

Chris_QPW

This an interesting problem, one that I suspect is much more complicated than it looks on the surface.

Without Quicken Inc and Intuit explaining how it is done (which they will never do) the best we can do is guess.

Here is my thinking/questions on it.

The first thing I would point out is people need to be absolutely sure that their data files are truly separate. Ether created with File → New File or Quicken’s copy command (not Windows copy and not a copy made by Quicken back when it didn’t crest a new unique file id and disconnect online services).

From what I have seen the financial institution knows nothing about your data file.

In fact, I don’t think they have any connection to Quicken whatsoever. They talk to Intuit. It is Intuit that they are exchanging security tokens with, and the transaction information as well.

The next part of this is it even possible for Intuit to have different security tokens per Quicken Cloud dataset???

This may or may not be part of the protocol, and even if it is possible different financial institutions might opt to not provide it.

Given that this is behaving for both of you with Fidelity and I know @Boatnmaniac knows to keep the data files separate then I have to assume if it is possible to keep them separate then at a minimum Fidelity hasn’t implemented it.

Note I said Quicken Cloud dataset, not Desktop data file. Quicken Inc servers/Cloud dataset are in between and do a sync to the Desktop data file.

Boatnmaniac

@Chris_QPW - Thanks for the additional comments and insights. It's always great to get other perspectives on things like this. In this case it's nice to see that we are largely on the same page.

Yes, a "cloudy" (please forgive the pun) vision on this is likely the best we'll ever have because, I agree, it is highly unlikely that Intuit/Quicken will ever provide us with that level of insight. This forum is a great place for us to hold discussions regarding our various observations and thoughts and eventually we can often reach some consensus on what the situation really is.