The 1Password Community forums are in read-only mode from Jan 28th - Feb 4th, 2025. Find out more.

Save more than 1 password on a website

Domon
Domon
Community Member

Hi,

How do I save more than 1 password on a website?

For example, on https://protonmail.ch/, I need my username and password to sign in, and then a mailbox password to decrypt my inbox.

I have added a custom field for the mailbox password. But I would like to know if there is a way to make 1Password automatically fill it in, like the sign-in form.

Thanks! :smile:

Comments

  • littlebobbytables
    littlebobbytables
    1Password Alumni

    Hi @Domon,

    I think what you're looking for is this guide, Creating a multi-page Login. It will cover the different approaches possible. If you have any follow up questions please do ask :smile:

  • Peter Stevens
    Peter Stevens
    Community Member

    Thank you - found this after posing same Q on twitter. Will give it a whirl :)

  • Drew_AG
    Drew_AG
    1Password Alumni

    @Peter Stevens, on behalf of littlebobbytables, you're very welcome! We're glad to help if you have more questions. :)

  • Domon
    Domon
    Community Member

    Hi @littlebobbytables,

    Thanks for your quick response! :)

    Actually, before asking the questions, I have tried the steps on the "Creating a multi-page Login" guide.
    On the Bank of America website, we enter an online ID in the first page, then passcode in the second page.

    However, it does not work in this case.
    On ProtonMail, I have to enter username and password in the first page, and then another password in the second page.

    When I followed the steps in the guide, 1Password overrode the first password with the second one.

    Probably I should create a second login item for the second password. But I would like to know if there is a way to keep them in the same item.
    For example, is there a way to manually add a new field to web form details, so that I could specify the name and value of the <input> tag in the page?

  • littlebobbytables
    littlebobbytables
    1Password Alumni

    Hi @Domon,

    I think the first thing to check is if it's possible at all. It might be a lot easier for you to check this bit given we're talking about multi-page logins (where I suspect I won't be able to get past the first page).

    Take ProtonMail. If you create two separate Login items using the Saving a Login Manually process and then view the web form details, will the field labels allow us to even try? If the label on both pages is password for example we've hit the limit of what we can achieve using a single Login page.

    With Bank of America I'm surprised to hear you're having troubles, partly just because we use that one as an example. Using this guide as an example, Using 1Password with login sequences split across multiple pages can you give me an idea how far down the steps you can get before it breaks down and diverges from the expected results. Certainly we'll try and work with you in both cases.

  • [Deleted User]
    [Deleted User]
    Community Member

    I'm having the same issue as @Domon with the 2nd password overriding the 1st. Is there a way we can assign a 1st password to https://protonmail.ch/login and a second password to https://protonmail.ch/locked in the same Login item in 1Password? For now I have to have 2 different logins which both show up on both of the previous URLs even though I assigned each a specific web address on which to be used (lenient URL matching is off for me).

  • Drew_AG
    Drew_AG
    1Password Alumni

    Hi @adam0293,

    Unfortunately it doesn't sound like it will be possible to have a single Login item that fills different passwords on both pages of that site. As littlebobbytables mentioned, if "password" is the field label on both pages, 1Password will see that as the same password. You'll need to keep a 2nd Login item to fill the second password on the second page. You can use a naming scheme for those Login items to help you tell which one is for which page, as described in the Help section at the bottom of these steps.

    The Lenient URL matching setting changes whether 1Password only looks at the main domain (for example, google.com) or also the subdomain (mail.google.com, accounts.google.com). Therefore, that setting won't make a difference for the protonmail.ch URLs you're using, since they don't have different subdomains.

    I'm sorry I don't have a better answer for you about that! If you have more questions or need anything else, please let us know.

  • [Deleted User]
    [Deleted User]
    Community Member

    A feature request: "Strict URL matching" configurable by item (e.g. on the ProtonMail login but not others) including URLs with the same subdomain.

  • Drew_AG
    Drew_AG
    1Password Alumni

    Thanks for the suggestion, we appreciate it! :) I can't make any promises of course, but I can forward that to our developers.

  • [Deleted User]
    [Deleted User]
    Community Member
    edited July 2015

    @Drew_AG: You mentioned that 1Password looks at the field labels to see which login data it should associate with which web form detail. I’ve encountered the same problem and I also looked for a way to make this work. From the source code I gather the following:

    Page 1 (where you have to enter your username and password):
    <input type="text" id="username" name="UserName">
    <input type="password" id="Password" name="Password">

    Page 2 (where you have to enter your encryption key):
    <input type="password" id="MailboxPassword" name="MailboxPassword">

    When I look at the web form details in my 1Password entry, I noticed the following two fields (there were more empty fields):
    UserName
    Password

    Based on the tag, shouldn’t 1Password be able to distinguish the “Password” field from the “MailboxPassword” field? I’ve tried it by changing one of the superfluous fields into MailboxPassword, but it still doesn’t work. 1Password will always use the password field.

  • Drew_AG
    Drew_AG
    1Password Alumni

    Hi @Eitot,

    Great question! It's hard to give you a definite answer without knowing more about how you created and edited that Login item. Since those three fields are split between two different pages on that site, you wouldn't normally end up with all three of those exact field labels in the web form details. But if I understand what you're saying, it sounds like you saved that Login item from "Page 1" (with your username & password), then edited that item in 1Password and changed one of the "empty" fields into the "MailboxPassword" field. Is that correct? (If not, please describe the exact steps you took to create/edit that Login item.)

    If that's what you did, is the problem that 1Password isn't able to fill the MailboxPassword field correctly on Page 2? Are the other fields filled correctly on Page 1?

    Also, would you be able to let us know the URL for that site? If so, we should be able to do a little testing there which might help. Thanks!

  • [Deleted User]
    [Deleted User]
    Community Member
    edited July 2015

    @Drew_AG: Yes, you are correct in all points. The problem is that 1Password correctly fills username and password on the first page, but on the second page wrongly enters the password again instead of the encryption key, even though the <input> fields distinguish between “Password” and “MailboxPassword”. I had hoped that 1Password would always attempt to match the web form details with the <input> fields, but it seems to prioritise the password field instead.

    In addition, I also followed the multi-page login guide (above) step by step, but when I attempt to update my 1Password entry while on the second page (step 2, point 3), it will simply override the password entry I created previously with the encryption key instead of adding another web form detail specifically for this. In other words, it treats the encryption key as a changed password and updates it accordingly.

    The URLs are: https://protonmail.ch/login and https://protonmail.ch/locked. Unfortunately, ProtonMail works with a reservation system, so it is not possible to create an account for testing purposes. The second page can only be accessed after logging in.

  • littlebobbytables
    littlebobbytables
    1Password Alumni

    Hi @Eitot,

    I hope you don't mind me jumping in here but I spend a bit of time in the Saving and Filling in Browsers and as a result have already pestered the devs with lots of questions :tongue:

    We have two key filling behaviours. One is where we make use of the web form details and we fill using that information to fill the page. This particular filling approach is quite strict in terms of when it's enabled, we use the web form details as a sort of fingerprint and the web page you're trying to fill this into has to match precisely. If the field fingerprints, for a lack of a better term, don't match then fall back on our more primitive filling which is where we will attempt to fill the contents of your username and password field and we use a number of rules of thumb to decide what fields are the correct ones to fill. That might sound a little odd but some pages combine both a register and log in panel on the single page.

    So by adding an additional field the fingerprint changes and we revert to the fallback behaviour which uses the username and password fields only. I believe this explains the behaviour you're witnessing.

    There is something I'm curious about, which ideally I would have tested before commenting on but given the situation with the site that could be a bit of a long wait. You seem pretty game for trying stuff so if you don't mind testing we can see the effect.

    1. Try creating a brand new Login item solely for the second page of the login process. This one will have the MailboxPassword field ID.
    2. Test to confirm this Login item works.
    3. Edit the Login item and click on the show web form details button.
    4. You will probably see the key symbol against the MailboxPassword field as 1Password will have designated this field your password. Click on the key symbol to bring up a small menu and select the blank option (so not the key or silhouette of the person).
    5. Click Save to save this change. You should see your password disappear from the top of the Login item.
    6. Edit the item again, it sounds odd but we needed to save the break between the web form details first before this step hence save and then edit again.
    7. Now fill in the username and password fields at the top of the Login item and use the credentials for the first page of the Login process.
    8. Save these changes.

    Now I can't guarantee it will work but I have this hunch that it might. On the first page we won't see the MailboxPassword so we should default to our fallback filling approach and user the username and password fields. What I'm hoping but can't easily test is that the second page will still work as normal. So this might strike out but we'll both learn something from it. Let us know how you get along :smile:

  • [Deleted User]
    [Deleted User]
    Community Member
    edited July 2015

    @littlebobbytables: Thanks for your explanation. I have followed your suggestion step by step, but, unfortunately, the result is still the same: the second page will be filled with the password, not the “MailboxPassword” field with the encryption key. It does work of course when I use two separate 1Password items, one for each page, but it’s just not the same automatic password filling that I want. I’ve attached a screenshot of the 1Password item.

  • littlebobbytables
    littlebobbytables
    1Password Alumni

    Hi @Eitot,

    I have to confess, because I couldn't see the second page it was a bit of a shot in the dark, I much prefer testing and knowing what I'm suggesting works. It sounds like for now you require two Login pages. Maybe at some point in the future we can alter part of the underlying filling behaviour but we'd have to be very careful as the last thing we want to do is accidentally break filling in some significant way in a bid to improve it. There may be security issues I've also not considered that come into play but of course that's up to the developers account for :smile: Anyway, I do apologise we couldn't come up with a more elegant solution.

This discussion has been closed.