Multi urls for login item
Hey,
how can I save an login item with multi urls?
In the documentation there's just a sample for one.
op create item [--title=] [--url=] [--vault=] [--tags=]
Does some got a hint for me?
Greetings
1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided
Comments
-
Currently that’s not possible with our CLI tool. Every item is separated into two parts, the overview and the details. We allow setting anything in the details, but only a few things in the overview. The URLs list is in the overview, and we currently only allow setting one.
This is something I want us to make better in a future release.
Rick
0 -
A digression on overviews and details
As Rick explained, we don't yet offer a way in the CLI to tinker much with the information in an item overview. We do have a mechanism for you to create or modify item details.1 So you might be wondering what this overview versus details thing is all about. If you are wondering, read on.
There is information which is private (such as the websites you have logins for, the titles that you give to these things) that are nice to have available quickly within 1Password. If you have an item for
https://nickelback-fans.org, you may not want anyone who gets a hold of your 1Password data to know that, but we want 1Password clients to quickly and easily see that you do have a item for that site and show you the item's Title.This sort of overview information is needed to construct an sort a listing of your items and to find thing website matches. Now none of this is relevant to the CLI, but it is very relevant to other 1Password clients. So the overview contains things like URLs, item Titles, and a few other things of that nature. Usernames, passwords, notes; on the other hand; are not in the overview. Those are in what we call the item details.
Some 1Password optional features require sharing decrypted overview information with other applications on your local device.
A history lesson
Back in the old days, when decryption was really slow and people didn't store data on other people's computers as much, we left that kind of information unencrypted. This was in the Agile Keychain Format. I should add that we tried to make this fact clear at the time instead of obfuscating the unencrypted data. So prior to late 2012, the kinds of data that we call "overview" now, was simply unencrypted meta data.
When we introduced OPVault in 2012 the world had changed. Computers were faster, AES in hardware was more common, and storing 1Password data on other people's computers (mostly Dropbox) was the norm. It less acceptable to continue the practice we did with the Agile Keychain, and 1Password clients had the computing resources to do better. We needed to also encrypt information like Title and URLs.
In OPVault we had all of the overviews encrypted with a key used just for that vault's overviews, which the details of each item was encrypted with its own item key. This allowed 1Password to decrypt the overviews all at once, while only decrypting individual items as needed. It also allowed us to construct a temporary table of overview information for quick lookup.
We preserve this distinction in with 1Password Accounts. As systems become more powerful, we can (more or less) get away with decrypting all item details in a vault at once even on most mobile devices without killing their batteries, but the distinction has become more useful in terms of network activity. Our clients can fetch just the encrypted overviews from a vault, without having to fetch all of the details of each item.
Anyway, this is why there are item details and item overviews, packaged and encrypted separately for each item.
-
I was mistaken in earlier version of this post. The CLI does not (yet) have the capacity for modifying existing items. ↩︎
0 -
