Add a pass backend as alternative to the Linux keyring to retrieve the shibboleth credentials

[Ma27]

Rather than using e.g. KWallet or gnome-keyring, I prefer to manage all my credentials with pass(1).

I'm not aware of any integration between the freedesktop secret-manager standard and pass, also it doesn't seem so uncommon to provide different backends depending on where to retrieve credentials, see for instance how aws-vault does this. The primary downside of course would be the increased maintenance load.

The integration could basically look like this:

KIT-ILIAS-downloader --keyring

for using the system keyring or

KIT-ILIAS-downloader -U uXXXX --pass-prefix edu/kit/uXXXX

with --pass-prefix and --keyring being mutually exclusive.

Would you be open to accept such a change? If yes, I may take some time soonish(tm) and implement that :)

[FliegendeWurst]

I'd accept this new option.

KIT-ILIAS-downloader/src/cli.rs

Line 150 in f21c024

pub fn ask_user_pass(opt: &Opt) -> Result<(String, String)> {

is probably a good starting point when implementing a new password backend.

Rather than using e.g. KWallet or gnome-keyring

FWIW, I'm currently using the secret service integration included in KeepassXC (because it can be set up to require confirmation on each password access, unlike KWallet).