API key persistence setting is global, not per fetcher

[kerollosy]

JabRef version

Latest development branch build (please note build date below)

Operating system

Windows

Details on version and operating system

Windows 11 25H2

Checked with the latest development build (copy version output from About dialog)

• I made a backup of my libraries before testing the latest development version.
• I have tested the latest development version and the problem persists

Steps to reproduce the behaviour

• Configure fetcher A as non-persistent, then B as persistent → the flag ends up true (B's dialog was last) → at save time, storeFetcherKeys() writes all custom keys to the keyring, since it only checks the one global flag, not each key individually → both end up persisted.
• Configure A as persistent, then B as non-persistent → the flag ends up false → the app wipes every key from the keyring, not just B's → both end up non-persistent.

Originally posted by @kerollosy in #16519 (comment)

[kerollosy]

/assign-me

[jabref-machine]

⚠️ Self-Assignment Not Allowed

Hi @kerollosy, you cannot self-assign an issue you created.

Note

This project requires maintainer approval before working on self-created issues to ensure alignment with the project roadmap.

What you can do

• Wait for a maintainer to review and approve your issue
• Ask a maintainer to assign you if the issue is approved
• Look for other existing issues to contribute to

[calixtus]

/assign @kerollosy

[jabref-machine]

Thank you for your continued work in JabRef. At this point, you probably already know the basics and the important links. If not, our contributing guidelines is the place you should go to.

At this point in time, you raised 2 pull request(s) of which 50% (1/2) have been merged.

[calixtus]

Hey, good catch. Thanks for your ongoing interest in JabRef!

[kerollosy]

Hey, good catch. Thanks for your ongoing interest in JabRef!

Thank you for the opportunity, I wish I knew JabRef earlier

[github-actions]

A pull request addressing the issue has been created. You can try out the pull request by following the steps at How to try out any JabRef pull request?.

For any feedback, add a comment to the pull request at #16616.