https://bugs.kde.org/show_bug.cgi?id=366326
--- Comment #3 from Jeff <jeffjl....@outlook.com> --- Mike: Yes, since Quicken already had a CLIENTUID for my accounts, and I had read elsewhere on the web that institutions tend to limit the number of UID's they accept per account (sometimes to one?), I set my KMM UID to what Quicken was using. I'm still unclear on where the UID came from - I believe Quicken just "made it up" through some hash of the account name or something (if I'm remembering correctly what I tried to decode from their documentation). And I'm not sure if there's some extra transaction required with the bank the first time you use a CLIENTUID. If there was, Quicken did it for me and/or told me how to do it. I seem to recall doing something - maybe it was just deleting the online setup in Quicken and re-establishing it when Chase changed their policy. But I vaguely recall going to the bank website and doing something too. Maybe it was just reauthorizing OFX access after the policy change. With some effort, I could make patch files. I'd need to back out all my other changes, but just the CLIENTUID changes are pretty simple. But my KMM patch just assumes that libofx supports the CLIENTUID (thus why I call it a hack). Not sure what is the best way for KMM to know or figure out if it's supported before trying to use it. (Originally I thought it could eventually just require a newer version of libofx before compiling that in.) I'll look into making patch files. -- You are receiving this mail because: You are watching all bug changes.
