Bug 413284 - user-manager should change kwallet password (if identical before)
Summary: user-manager should change kwallet password (if identical before)
Status: RESOLVED DUPLICATE of bug 389030
Alias: None
Product: user-manager
Classification: Plasma
Component: kcontrol module (show other bugs)
Version: 5.17.0
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: Jonathan Riddell
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-10-21 15:14 UTC by kolAflash
Modified: 2019-10-27 23:31 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kolAflash 2019-10-21 15:14:33 UTC
If a user has an identical user password and kwallet password, a user password change should also alter the kwallet password.

Especially with kwallet-pam, using kwallet becomes intuitive. So users get comfort and security without the need to know that there's something called kwallet. But if a user changes his login password, this nice world is being broken. Now the user will be asked to open kwallet explicitly to make things work (e.g. wifi login). And many users won't even have a clue about the whole password store concept.

Scenario is, that a user changes the own password using user-manager. In this case, it should just be checked if the kwallet password is identical and if, it should be changed too.
To make this work it's maybe helpful to also solve bug 378984. If done so, the user password (which may be needed to open kwallet) will be always provided on changing the own user password.

Maybe related:
- Bug 364376 - After changing the user password KWallet can't be opened any more.
- Bug 378984 - Root password required for user Password change
Comment 1 kolAflash 2019-10-21 15:20:44 UTC
KWallet ticket for what to do if the user password wasn't changed by the user herself, using user-manager:
Bug 413285 - ask what to do if user password became different
Comment 2 Nate Graham 2019-10-27 23:31:13 UTC

*** This bug has been marked as a duplicate of bug 389030 ***