Expiry Date Notification

Fairgame

We love this feature. Is there a way to add this to "user selectable" field so other categories such as Login could use this feature?
If not, would you please add this in the future.
Thank you

For reference from your Support website:

Expiring shows items that are expiring soon, so you can take action:
credit cards, memberships, and drivers licenses that are expiring within 2 months
passports expiring within 9 months
items that have already expired

---

1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided

Lars

@Fairgame - glad to hear you like it! It's a great thing for I can certainly mention it to the development team, but the main reason we didn't include Login items in the "Expiring" section is twofold:

1. Both we and NIST believe that if a user chooses a strong, unique password for each site (as we advocate here), and that password is not disclosed and the site itself is not breached in a way that discloses user passwords, there is little reason to change passwords at all, let alone change them on an arbitrary schedule. As a result of this,
2. The 1Password Login item template (and templates for other non-recurring-period items, such as Secure Notes or Databases) do not include an "Expiration" field.

To change this, we'd have to make changes involving design as well as database across four different native 1Password apps (Mac, Windows, iOS and Android), as well as 1Password X and the 1password.com server back-end. This wouldn't be a trivial undertaking. And so, as time goes on and webmasters become aware of better identity/authentication practices, fewer and fewer websites are requiring users to change their passwords regularly. Thus, I doubt we'll be making these changes in the foreseeable future. I do appreciate the suggestion, however! :)

Fairgame

Lars,
Thank you for your reply. I understand (sort of :)) the difficulty of making changes to the existing software and all the versions.
As far as the logins, I did not intend to use the expiring field for passwords, rather for a paid account with login that requires renewal, eg. magazines, insurance, online subscriptions etc.
Right now, the workaround is to have each item twice, as a login and as a subscription.

Another option might be to be able to “link” certain items from the login to the membership categories and have an expiration field tied to a login category that way.

Thank you

Lars

@Fairgame - we've got changes we're considering that will allow considerably more flexibility with item templates, so this may very well be something that could be incorporated into those changes, and it's an interesting idea. I'd assumed you meant forcing password changes, since Login items don't have expirations in the same way that Credit Cards do, but you're entirely correct in pointing out that while the passwords themselves don't (and shouldn't) expire arbitrarily, sometimes some of the items for which we all have Login items are themselves what expires. Thanks for bringing it up!

In the meantime, another approach to this (instead of creating two items) would be to use Tags to accomplish the same thing. For item types that don't support the expiration date field that shows in Watchtower, you could add expires-november or expires-february tags, which would then be searchable in 1Password. You can also add a "Date" field to any item, to give it a precise date (e.g. 11/25/2019, etc) which could serve as the expiration date. You'd have to remember to check this manually once a month, but this would give you a pretty reliable system as long as you remembered to add the tags and the date field when you create the item, and check it once a month or so. Sorry that's not quite as elegant a solution, and thanks for the suggestion!

Fairgame

Thank you for suggestion and for possibly adding this to your “todo” list.

ag_ana

:+1: :)