OwnCloud client on Debian/KDE : store password without KWallet, GNOME Keyring etc.?

Desktop
1

Hi,

My important data are on an OwnCloud server. I recently migrated my workstation from Rocky Linux 9 (with KDE from EPEL) to Debian 13 Trixie KDE. I installed the OwnCloud client to synchronize my data.

Normally I don’t use KWallet, GNOME keyring or similar password agents. On my old Rocky Linux 9 installation, once I configured my OwnCloud account and submitted my OwnCloud login and password, the account synchronized perfectly. Then in subsequent sessions the OwnCloud client connected automatically, without me having to type either the login or the password again. I guess the credentials were stored somewhere under the hood in ~/.config/owncloud.

I’d like to have that same behavior on my Debian 13 KDE workstation. I have no KWallet, no GNOME Keyring or similar. Now everytime I start a KDE session, OwnCloud client pops up and wants to know my credentials again. I really don’t want to type these in again at every session start. I don’t mind if the credentials are stored under the hood in ~/.config/owncloud. This workstation is in my office, and I’m the only one who has physical access to it (besides the fact that I already use credentials to start my user session).

How can I change this annoying behavior ?

Cheers,

Niki

2

When running on Debian KDE, the OwnCloud app will store passwords in either KWallet or GNOME Keyring by default. If neither of them is found, it won’t use plaintext in `~/.config/owncloud` like it did on Rocky Linux. Right now, the only ways to get storage “under the hood” are to either use a lightweight keyring (like `kwallet-pam`) that opens with your session or patch the client to allow plaintext storage. However, in newer versions of ownCloud, you can’t store passwords without a keyring out of the box.

1 Like