Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Feature Request: Proactive Expiry Events for Service Account Tokens in Events API
Hi 1Password Team, I am managing 1Password integrations in a Kubernetes environment. We currently use the Events API to stream logs into our centralized observability platform (VictoriaLogs). The Problem: The current Events API is action-based. For Service Account Tokens, there is no proactive event (like "Token Expiring Soon") via the API. We only discover a token has expired when our controllers log a 401 error: "status 401: Authentication: (Invalid bearer token), go-jose/go-jose/jwt: validation failed, token is expired (exp)" Feature Requests: Status-based Events: Does 1Password plan to support proactive events such as "service_account.token.expiring_soon"? Webhook Support: Are there plans for Webhooks to alert on critical auth failures or lifecycle changes? Audit Log Coverage: Can "System-triggered Expiry" be added as an action in the Audit Log? Our goal is to prevent production incidents caused by expired credentials. Looking forward to your insights.
Finding Almost Duplicates
Hello All, I support 1Password in our company of mostly Mac computers. (new to it myself, though) We have a user on a Macbook Air who imported passwords three times over the last year. (I'll give him credit. He's trying!) Each import does have a tag with the import date. I want to remove the old duplicated items from his vault. Watchtower does not show any duplicates. My guess, I haven't confirmed yet, that the items are not exact duplicates. Certainly the tags are different. (Hmm, maybe if I delete the tags they would become duplicates?) I don't want to just delete all items with an old tag because I I can't confirm that all the old ones (> 300 items) have new versions. Maybe there's a way to do that? Maybe we export all of them, delete duplicates in Excel, delete all in 1Password, and then import them again? I'm liking this option. When he did the imports, it didn't keep the Titles. It made new Titles with the website+username (I think). Yuck! Screwed up his logins for apps. This brings up a missing feature. When 1Password imports items, it would be good if it recognized the duplicates at that time and then give options on what to do with them, e.g. not import, keep newest, keep oldest, keep both, merge (?). I'm sure there's a feature request site somewhere. Thank you for any advice.
Feature request: scheduled report delivery
For compliance and remediation we're required to gather 1Password reports and follow up with end users regarding usage and password hygiene. I'd like to have business watchtower and usage reports sent to our ticketing system for tracking and documentation on a monthly basis.