Bug 391454 - passwords not integrating (storing) with KMM 5.0 and KDEWallet properly
Summary: passwords not integrating (storing) with KMM 5.0 and KDEWallet properly
Status: RESOLVED DUPLICATE of bug 392603
Alias: None
Product: kmymoney
Classification: Applications
Component: bugtracker (show other bugs)
Version: 5.0.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-05 21:24 UTC by Michael Carpino
Modified: 2018-04-01 11:57 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Carpino 2018-03-05 21:24:44 UTC
After Mapping a Brokerage account (checking & investment)using OFX the passwords don't appear to be linking correctly with KMM.  I input the information (ID & Password) and update (download) the transactions which works fine.  Then I come back again to update and it shows the account is mapped but the "Update account" is greyed out.  If I select Update all accounts it asks me to select the checking account associated with an unidentifiable account. The only workaround is to unmap, remap and download the transaction each time.

Passwords are properly stored in KDEWallet.
Comment 1 Jack 2018-03-05 21:43:58 UTC
I think the issue of KMM asking for the user to identify the checking account is a separate bug (I do not think yet reported, but I think I mentioned it on the mailing list) where it should automatically choose the Brokerage account for the Investment account being processed.

I also think I reported to the mailing list the issue that accounts which were mapped in 4.8 did not show as mapped in 5.0.  However, that issue was fixed in 5.0, even though it seems at least partly similar here.  

Also, please clarify which OFX you are using, and your process to map the account.  From memory, you have to specify the ID and password when you map the account, and it should save them then.  If you have to specify them again when actually updating the account the first time, then there might be some problem with password storage.  I know I have not had any problem udpating accounts (OFX, not aqbanking) with 5.0.
Comment 2 Michael Carpino 2018-03-05 23:04:13 UTC
I tried a few different things which is appears to cause a linking issue or lack there of. First I deleted the passwords in KDEWallet to make sure the passwords where being set there correctly.  Then I unmapped the investment accounts.  

With my first brokerage account(TD Ameritrade),  I went the checking account and mapped the checking account by selecting account > map account > ofximporter > TD Ameritrade. After finalizing I verified that I can update and it works.  But if I go to the Investment Ledger for this account it is still showing Unmapped.  I can go through all the steps and map it but there is some type of linkage problem I didn't have to do this in earlier versions. 

With my other brokerage account (Fidelity NetBenefits) I went through the same steps above except I started by mapping the Investment ledger.  Then I went to the (brokerage) checking account and it shows it isn't mapped.

When I look in KDEWallet the paswords are stored there correctly.

I have other accounts that are not "Brokerage" type and mapping is working just fine.
Comment 3 Jack 2018-03-05 23:13:14 UTC
So we need to fix the docs somehow, to make it clear how to handle this situation.  You should ONLY map the investment account, and NOT the brokerage (checking) account.  When you download, any cash transactions are correctly put in the associated brokerage account.  (At least they used to be.  Now, you may need to specify the brokerage account when KMM asks what checking account to use when you do the first update.)
Comment 4 Michael Carpino 2018-03-05 23:26:52 UTC
Yes, I dualboot and went to my windows 10 KMM 4.8.1.1 and the transactions are going into the investment account as you stated.  With 5.0 the issue is it asks everytime what checking account you want to use.  And there is no description on what account its referring to so you're clueless when you have more than 2 on what to do.
Comment 5 Michael Carpino 2018-03-05 23:35:26 UTC
With 5.0 the only way to kinda getting it to work is to Map both accounts (Brokerage and Investment) and the transactions are dumped into the checking account.
Comment 6 Jack 2018-03-06 00:51:21 UTC
I strongly suspect, but have no proof, that you will end up with more problems if you map the brokerage account.  (In fact, I believe that KMM should warn you if yo do try to map a brokerage account, but it seem to only know that if you accept the default name for it, which is "(Brokerage)" appended to the name of the investment account.  I don't know if there is a bug filed already for KMM asking where to put the "checking" transactions.  If you only update one account at a time, you can know which brokerage account to specify, so until this is sorted, I would just advise against updating all at once.

Also,, you should not be able to map more than one KMM account to the same online account, or else it wouldn't know which account to use.  (That is true in general, although Investment accounts are of course different...)
Comment 7 Michael Carpino 2018-03-06 01:00:05 UTC
Ok I'll take your advice and unmap the brokerage/checking account and update the accounts 1 account at a time.
Comment 8 Michael Carpino 2018-04-01 11:56:12 UTC
I've defined the problem better with a different bug and marked this as a duplicate.
Comment 9 Michael Carpino 2018-04-01 11:57:16 UTC

*** This bug has been marked as a duplicate of bug 392603 ***