Open radoeka opened 2 years ago
This is already a feature since 2.7.0. It works great, but will only show on FIRST unlock.
This is already a feature since 2.7.0. It works great, but will only show on FIRST unlock.
Before opening this request, I searched the documentation, bug reports and more, but did hardly find anything about this.
I locked my keepassxc, and unlocked, nothing about expiring passwords. Searched the menu, nothing about expiring passwords.
The unlocking on first opening only, is on a computer that's hibernated most of the time hardly used.
Just now, when I closed the DB and opened it again: there it is indeed. Nice. However, it shows expired passwords that are now longer used. Would it be possible to set a window in which the expiring and expired windows are shown? E.g. 14 days before expiring and 1 month after expiring. The before is already there, the after not. Could that be added?
When I delete an expired entry in the expired password list that is shown after opening the DB, the list is gone as soon as the entry is deleted. To continue, I need to close keepassxc, opening the DB and delete another entry. I think this can be friendlier.
Isn't the current functionality than lacking functionality? E.g. a description in the documentation (if the description exists already, can you provide a link to it, please), would it be possible to add a menu option 'view password(s) that are going to expire'? If the before mentioned functionalities are possible to be added (if missing), let me know please. What would be a way forward to get this functionality in keepassxc, multiple feature requests maybe ( I'm not going to code nor document ).
I've already made several enhancements to this experience in a pending PR I have for tags and searching. I will add showing the report once per week on unlock (in addition to every fresh unlock).
If you like to keep your expired entries in your db, recommend making a group (Archive) and disabling search of that group. Then drag/drop all expired entries into that group. We won't implement expired max/min settings.
Thanks for re-opening the issue.
I also now found the 'Expired' Database tag. Which gives the information that I was looking for. I expected this in the menu 'view'.
Thanks for the hint about the non searchable archive folder. With your hint I would never have come up with this idea.
Summary
When a password expiry date is set, the keepass entry is strike through when the entry passed the set expiry date.
When that signal comes in, it is too late as the password already expired.
If a lead-time could be configured, the signal that the password is going to expire is sent in time, and the user can change the password before it is actually expired.
At the main settngs page, there is a setting: 'On database unlock, show entries that will expire in N days' But this is not working of me.
Examples
password expires at 1 August 2022.
Lead-time: 5 days the keepass entry before 27 July is shown in normal characters the keepass entry up and after 27 July 2022 is shown in strike through
In the window "Edit Entry' at the Expires line, between the date picker and the presets dropdown menu, add a menu to set the lead time for this entry. Provide the menu in days for flexibility (user editable).
Perhaps, a default lead-time can be set globally to for example 14 days.
A view option, that shows the passwords that are expiring soon, including the lead time.
Context
I don't want my applications to be not accessible as keepass would trigger/signal just in time that the password expires. Perhaps this is in a weekend, or a holiday or a day when I do not open the keepass. The leadtime takes care the user is signalled in time, that her/his password is about to expire.
( Workaround at the moment, set the expiring date X days in advance. But by doing show, I loose the information when the password is really expiring. And thus I store the real expire date in the notes. But this really feels like a workaround. )
Related
1483 Notification for soon-to-expire passwords