Forum Discussion

Former Member's avatar
Former Member
5 years ago

[27] Secondary URLs for Autofill

Hi 1Password-Team,
Thanks for your work on the CLI v2 and thanks for letting me participate in the Beta.

We'd like the ability to add a secondary URL / Domain / Website to each 1Password Login entry.

As a bit of background: We use 1Password to store our Admin logins to our customer's website instances.
Each customer website is reachable via our 'internal domain' (https://cosaprod.recollect.net.au/)
as well as their custom domain ('https://archives.cityofsydney.nsw.gov.au/')

I am able to manually edit an item in the GUI (by clicking "+ add another website"), which then shows up in the CLI as multiple entries under "urls"
op item get "City of Sydney Archives"
[...]
urls:
- primary: false
url: https://archives.cityofsydney.nsw.gov.au/
- primary: true
url: https://cosaprod.recollect.net.au/

Adding them manually via the GUI ensures that 1Password Chrome Extension Autofill works for all domains.

If I try to add them via CLI I'm only able to add them to a custom section, with type URL.

Adding these customURLs looks as follows:
op item create \
--category=login \
--vault "$Vault" \
--title="$Title" \
Username="$Username" \
Password="$Password" \
URL="https://${CustomerTheme}.${RecollectDomain}/" \
CustomDomain[url]="https://${CustomDomain}/"

then the result looks as follows:
op item get "City of Sydney Archives"
[...]
- id: 5xpln5qr26gnxr4is6thsmuabm
section:
id: Section_2ofnhlujwwxrd6lzqbmg7sow5q
label: ""
type: URL
label: CustomDomain
value: https://archives.cityofsydney.nsw.gov.au/
urls:
- primary: true
url: https://cosaprod.recollect.net.au/

Unfortunately this custom URL does not seem to be considered by the 1Password Chrome Extension Autofill.

As your CLI Documentation says I've tried around with modifying templates, specifying URLs as part of the json template, but I've not managed to get that to work.

With CLI v1 the way I understood it, adding a custom domain (for use in Autofill) was unsupported.
With CLI v2 I feel it should work but I can't work out the correct way.
I'd appreciate some help / explanation.
If it's still not supported that would also be an answer, then at least I can stop trying around.

Thanks so much for your help!

Cheers,
Dominik

1Password Version: 2.0.0-beta.6
Extension Version: Not Provided
OS Version: Ubuntu 20

cli

2 Replies

  • Former Member's avatar
    Former Member
    5 years ago

    Hey Simon,

    Thanks for your explanation.

    Hell yeah would I love to test that new feature when it's ready ;)

    Cheers,
    Dominik

  • 1P_Simon's avatar
    1P_Simon
    Icon for 1Password Team rank1Password Team
    5 years ago

    Hi Dominik,

    Adding a second URL for auto-fill via the CLI is not currently supported.

    Thanks for sharing such a detailed description of what you'd like to achieve and what you tried to do to get that to work. This gives us very valuable insight in what we can improve here.

    1Password currently knows to types of URLs for items:
    1. URL fields, that allow you to store a URL together with the item. These are not used for auto-fill in the browser.
    2. URLs used for auto-fill, that you see under the url keyword when fetching an item using the CLI. These URLs are currently not considered fields.

    Using the CLI, starting in v2 you can set URL fields using the syntax you tried as well CustomDomain[url]="https://${CustomDomain}/. In both v1 and v2 you can set URL fields using an item template.

    URLs used for auto-fill are currently configured in the CLI using the --url flag. This supports only a single value currently.

    We'll look into both making the difference between these two types of URLs clearer and making the configuration and behavior of the two more consistent (e.g. be able to configure both using the new field[type]=value syntax) as well as into supporting to configure multiple URLs used for auto-fill. When we have a new design ready, would you be willing to give it a look and let us know what you think?

    Thanks again for providing such a descriptive feedback!

    Cheers,
    Simon