Bug 440710

Summary:	Aqbanking: kmm should not cache/remember the password if it was incorrect
Product:	[Applications] kmymoney	Reporter:	Dawid Wróbel <me>
Component:	onlinebanking	Assignee:	KMyMoney Devel Mailing List <kmymoney-devel>
Status:	REOPENED ---
Severity:	normal	CC:	juantxorena, kde, st.vater
Priority:	NOR
Version First Reported In:	5.1.2
Target Milestone:	---
Platform:	Other
OS:	Other
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Dawid Wróbel 2021-08-07 20:14:34 UTC

SUMMARY
If you type in an incorrect password to an account configured with kbanking (aqbanking), KMyMoney will remember it until restarting.


STEPS TO REPRODUCE
1. Map an account with kmymoney and configure it to ask for the password each time
2. Attempt to update account and provide wrong password
3. Attempt to update account again

OBSERVED RESULT
The app doesn't ask for the password again, despite the previous attempt clearly having failed due to a wrong password

EXPECTED RESULT
The app should not cache the incorrect password and ask it again

Comment 1 Moritz Bunkus 2021-09-03 18:51:34 UTC

Doesn't this look like a duplicate of bug 384051?

Comment 2 juantxorena 2025-03-07 10:40:39 UTC

(In reply to Moritz Bunkus from comment #1)
> Doesn't this look like a duplicate of bug 384051?

I don't know if this is a duplicate or not, but the problem still exists.

Comment 3 Thomas Baumgart 2025-03-07 16:34:02 UTC

How can this still exist if it has been fixed in Gwenhywfar/AqBanking? I also remember to have mistyped a password lately and was able to re-enter it. I don't run into this problem since using KMyMoney's integration with pass (https://www.passwordstore.org/).

BTW, here's the commit message of the fix:

commit f0c8a65ada0b8387199b028a117df42a1f9ab468
Author: Martin Preuss <martin@aquamaniac.de>
Date:   Sun Sep 5 19:33:35 2021 +0200

    GUI: Remove bad pin also from password cache.

Comment 4 Bug Janitor Service 2025-03-22 03:46:35 UTC

🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!

Comment 5 Bug Janitor Service 2025-04-06 03:46:36 UTC

🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.

Comment 6 Stefan Vater 2025-11-08 09:25:20 UTC

I have the same problem, as long as I use kmymoney with hbci with aqbanking. What infos can I give you to debug the problem?

What do you mean by "KMyMoney's integration with pass"? Do I have to setup something for this? I would like to reenter my hbci password every session I am using it.

Comment 7 Stefan Vater 2025-11-08 09:26:45 UTC

Ba the way, I am using KMM 5.2.1 with aqbanking 6.7.7beta for openSUSE tumbleweed repos.

Comment 8 Thomas Baumgart 2025-11-16 07:47:25 UTC

(In reply to Stefan Vater from comment #6)
> What do you mean by "KMyMoney's integration with pass"? Do I have to setup
> something for this? I would like to reenter my hbci password every session I
> am using it.

Pass is a password store based on GPG. You open the store with a master passphrase and it will remain open for some time. In that time, you don't have to enter any password at all. So I am not sure if it would suit your purpose. Of course, a changed password at the bank needs to be taken care of in the password store, otherwise you are in trouble.

BTW, using pass does not bypass the password cache in AqBanking which is the source of your problem.