Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
Can't set "purchase date" field expiry in future
I tried to set an 'expiry date' on the purchase date field of a license key, but it doesn't seem to let me set it in the future using the date selection. When I tried manually typing in the date, it seems to cut off the last number of the year. Starting Point: After selecting 'On a date' in the dropdown, any future dates are not able to be selected: If I try to manually type in the year as 2028, notice how the blue bar has already truncated off the 8 and set the year as "202". If I click out of the box to unfocus it which seems to finalize the date entry, then click to open it again, it has indeed set the date to literally "202", not 2028. This is not simply a cosmetic issue of the date appearing cut off, it literally truncated the date data to the year 202 (because today is not thursday). I suspect it's because the" purchase date" field is special and has some restriction to not allow it to be in the future, and therefore the attached expiry date is inheriting the same restriction. Because when I create a new custom 'date' field myself, it does allow me to set the date into the future. However, I can't figure out how to set an alert on a regular custom made date field: Version Details: 1Password for Windows 8.11.8 (81108040) ------------ EDIT: Ok actually I figured out how to set an expiry date on the custom field. It seems to only let me after I remove the alert on the 'purchase date' field:
Want to rely on Hello, avoid master password entry after reboot
While I appreciate others may have different security models (shared machines, etc.), in my situation Windows Hello (+tpm +bitlocker +secure boot) is the vetted gateway to everything. Via Windows Hello I have access to information more sensitive than even my 1Password vault, and I am satisfied with that. Also, for unrelated reasons, I reboot my machine frequently. If you combine these factors, you can see where I am going. I don't like the requirement to re-enter 1Password master password on every boot. It appears that this is by design. In the Settings view even when "Unlock using Windows Hello" is selected it says I will need to enter my 1Password password on every boot. As a feature request, I vote for an option to defer to OS+HW security here in terms of unlocking my vault/app. Alternatively, if there is some sound cryptographic reason it needs to be separate (even in my use case) I am open to being convinced.
Duplicate entries after imports
I'm new for 1password. I imported my passwords from Bitwarden and my Google account and now I have dozen of duplicated entries. I tried to use a Watchtower but it doesn't see any duplicates at all. The duplicated items are different in tags and time of editing and might that is the problem. Any way to delete the duplicates despite of the differences? Can I define to the Watchtower search the fields that are relevant for comparison (or event better the fields that aren't relevant)? Thanks ahead for the help!1password extension keeps locking in Remote Desktop session
The 1password is working in power automate desktop app when we run flow in power automate, but not in unattended on Remote desktop. I can't do a screen recording of the power automate flow running unattended. However, when the flow is ran we have set up an action to screenshot where the error occurred/flow failed. This is an example above. On desktop app the 1password is unlocked and will allow us to tab down enter to click the password for this login, however, in unattended mode- the screenshot above clearly shows that 1password is locked and it doesn't allow us to click on button to unlock it. This means the flow can't log us in so it then fails. Therefore, I'm assuming the issue is that 1password locks itself in unattended mode so we need it to be unlocked all time for our flows to run on rds when we run things overnight.When we checked settings in 1password app on the remote desktop it is set to 'Never' for locking so we are confused as to what is happening. Confused as to why it will not stay unlocked. Any help and guidance would be deeply appreciated. Thanks
German translation issue on Identity
As you can see, selection criteria and texts are in English on German language in Identity item. Could you please correct them? Also, it would be nice if you can add passport details, ID card details, social security numbers (Versicherungsnummer), tax identification number (Steuernummer or Steuerliche Identifikationsnummer), and so on to the Identity item.
