How can I set 1Password to fill an arbitrary field with a saved value?

I can't seem to find an exact answer to this question after searching through the support community postings, but here's my situation:
1. A particular website has a non-standard field that needs to be filled, i.e., one that doesn't have a recognized label such as "username".
2. As such, 1Password is unable to determine where to fill my username value.
3. I have tried the only solution suggested, which is to select the 1Password "save login" option before submitting credentials, to no avail.
4. My previous password management tool, LastPass, had the ability to save any form field information from a page. I can't seem to find a corresponding feature within 1Password. Am I basically out of luck?

In case an example is needed, let me provide one:
1. A website, JazzPenguinSite.com, provides a user login field coded in HTML as <input name="FunkyOstrichField" type='"text">.
2. Not surprisingly, 1Password fails to recognize "FunkyOstrichField" as the label for the username field.
3. In an ideal world, I'd be able to go to the settings of my password manager record for JazzPenguinSite.com and add "FunkyOstrichFIeld" as a field label that should be filled with my username, "ClassicalMongoose".
4. Is there a setting in 1Password where I can enter something like FIELD_TO_FILL:"FunkyOstrichField", VALUE_TO_USE="ClassicalMongoose"?


1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Browser:_ Not Provided

Comments

  • Joy_1P
    Joy_1P
    1Password Alumni

    Hey @franklaw, 1Password does have the ability to save and fill non-login fields. In some cases, 1Password will save these details automatically. In some cases, you will have to create a custom field in order to add these details to your login.

    Please note that while it is possible to create a custom field in the item to hold your info, we can't guarantee that it will fill. The success of filling the custom field is largely dependent on how the form in question is coded. The example you gave unfortunately doesn't provide us enough information to give you a specific answer. Do you have a link to a live form on which an issue like this appears? If so, please let us know.

  • franklaw
    franklaw
    Community Member

    I assume this means the answer is no, then, with respect to 1Password being able to fill arbitrary HTML input fields? It sounds like you need to process each site on a case-by-case basis. That sounds like a lot of work.
    An example of a site that runs into problems is this: https://seicashmanagement.mybankingservices.com/
    The HTML in question, I believe, is

  • Joy_1P
    Joy_1P
    1Password Alumni

    @franklaw 1Password does indeed go through the HTML on all sites on a case-by-case basis in order to save and fill. For the website that you shared, I can see that 1Password doesn't recognize the username field. I've reported the field and website to our developers. Hopefully, we'll be able to adjust some things on our end to improve the saving and filling experience there.

    For now, I recommend setting up the login item in the following way:

    1. Open the 1Password app and click 'New Item' > 'Login'.
    2. At the top of the login, make sure that the username field is blank.
    3. Fill in the password field (for now).
    4. Add 'https://seicashmanagement.mybankingservices.com' to the Website section.
    5. Click 'Add More' and select 'Text'.
    6. In the text field that appears, add 'ctl00$login1$txtUser' as the title.
    7. Add your username as the value.
    8. Save the item.

    This is an example of what the login item would look like: https://share.cleanshot.com/T3V8dfm6

    To fill that login, go to the website, click on the 1Password icon in your browser's toolbar, locate the login, and click Autofill. Alternatively, you can go to the website and use a keyboard shortcut to fill.

    Here's a video of both filling methods: https://share.cleanshot.com/nVgQkwSg

    I hope that helps. Let us know if you have any other questions.

    ref: dev/core/core#20783

This discussion has been closed.