I'm a KDE user and void like to avoid running any additional keyring daemons.
Chrome had a bug in the past and would choose a wrong password manager. It might happen with other software as well. I also see no use of this function because teams didn't manage to save my password even I ticked the required box and /usr/bin/gnome-keyring-daemon is running.
Currently, I have "-gnome-keyring" global flag, and teams is the only software which pulls app-crypt/libsecret.
Meanwhile, the solution was discussed in the previoud bug:
But the conversation died out. So I'm filling this bug to revisit it.
Please introduce "gnome-keyring" use flag and make libsecret dependency optional.
Would be nice, sure. But the question is: Why isn't teams storing your password?
I am on Plasma, too, and this feature works just fine.
By the way: The bug you mentioned was about removing the usage of the long deprecated libgnome-keyring when libsecret support was already in the teams client.
However, making the dependency on libsecret optional sounds reasonable to me.
I tried this out in my overlay seden (via layman) and had to revert immediately.
Without libsecret and after removing the keytar4 archive that uses it, the teams client no longer starts up.
You can try it out yourself by fetching my overlay and checking out commit 3518e1b5bffa246664535523f4c0a67c01618a60
( https://gitweb.gentoo.org/user/seden.git/commit/?id=3518e1b5bffa246664535523f4c0a67c01618a60 )
Sorry, but I guess the libsecret dependency has to stay.
__But__: I only tested briefly, as I need a functional MS Teams. So there might be a possibility to get rid of libsecret that I did not notice.
I found a libsecret bug filed here:
That's exactly what I want.
*** This bug has been marked as a duplicate of bug 705132 ***