-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding URLs to LOGIN items not working #49
Comments
Hey @gaborpeter - thanks for reporting this. We definitely should highlight the difference between I'll make sure this is included in the next update. |
Thank you @verkaufer ! |
Could you open that as a separate issue? Then we'll definitely see what we can do :) |
In fact I realised, even the 1Password API doesn't support adding labels to URL objects, so first I'll try my luck there. Once the API supports it I'll raise a ticket here. Thanks :) |
Hey @gaborpeter, Starting with Connect 1.5.1, 1Password API supports adding label to autofill URL objects. Thank you for your patience. |
Thank you it is indeed great news, will help to keep things more organised. |
Summary
After adding a LOGIN item with Ansible, and then visiting the site with the browser, 1Password client was not pulling it up as a suggestion even though the item was present and URL was correct.
Use cases
I followed the documentation how to create the item:
It did successfully create the item, but it added it under an empty "section" even though in the definition no section assignment was requested. After analyzing the tool I've seen that, you can add the URL's outside of sections and when they are placed there (kind of root level) then it works like a charm.
Proposed solution
I found in the 1Password API documentation that there is an "url" property for each item, which can be used. So when I added an item as follows, it did the trick and 1Password client suggested the item after properly when visiting the URL:
Probably this could be added to the documentation.
The text was updated successfully, but these errors were encountered: