Forum Discussion

connrs's avatar
connrs
New Contributor
10 months ago

Edge extension I can't update passwords when passwords change

I work for a company that has a lot of passwords for a lot of accounts. Many of those accounts sit on subdomains.

After successfully logging into a site with a saved password, I'll often be prompted to reset my password (due to a 90 day expiration policy).

I will follow 1Password's prompt to use a recommended auto-generated password and once I select that password, 1Password will open up a UI on the right hand side of the web page asking me which password needs updating.

There is no ability to scroll that list even on a 4K monitor. This means I can't see the buttons at the bottom and I also can't locate the password.

Does somebody know if there's a way to "scroll" or "search" the panel?

1Password Version: 8.10.44
Extension Version: 2.27.1
OS Version: Windows
Browser: Edge

browser extension

4 Replies

  • 1P_Dave's avatar
    1P_Dave
    Icon for Moderator rankModerator
    9 months ago

    connrs

    I'm glad that my colleagues over on the email side of things were able to help. 🙂

    However, in some circumstances (where 2 systems are sitting behind an Apache/Nginx proxy_pass subfolder location and neither system uses SSO for reasons) this means that the same subdomain but different folder paths exist. In some cases this causes - from my perspective - a match for a credential that I know isn't applicable.

    I can see how the autofill behaviours feature could be refined to also match based on folder paths rather than domain/subdomain. While I can't make any promises, I've filed a feature request on your behalf. Thank you for the feedback!

    -Dave

    ref: PB-42252905

  • connrs's avatar
    connrs
    New Contributor
    9 months ago

    Hi Dave,

    Thanks for the reply. I ended up contacting the very helpful support team and one of your colleagues filled me in with a suggested workaround along with details of the solution being in the pipeline (coming soonâ„¢!). However, I really appreciate you updating this post.

    Kind regards,
    connrs.

    P.S. Thanks for sharing the autofill behaviour link. This is the not 100% I was referring to but is my fault for calling it strict domain matching instead of strict URL matching. I didn't want to turn this post into a whinge about this feature because I'm actually comfortable with this and nobody at my business is unable to get their jobs done without it.

    However, in some circumstances (where 2 systems are sitting behind an Apache/Nginx proxy_pass subfolder location and neither system uses SSO for reasons) this means that the same subdomain but different folder paths exist. In some cases this causes - from my perspective - a match for a credential that I know isn't applicable.

    Again reiterating that it's not a problem. While this is a feature I remember from LastPass Enterprise (who we left a decade ago and definitely won't consider returning to while I'm in my post) it isn't in the 1Password feature set. If you ever implemented it then I'd be the 1 (and only 1) person at our business who cared…

  • 1P_Dave's avatar
    1P_Dave
    Icon for Moderator rankModerator
    9 months ago

    Hello connrs! 👋

    I'm sorry that you're unable to scroll through your list of logins. This is a known issue that our development team is working to resolve. We're currently testing the fix in the latest beta if you'd like to give that a try:

    1Password doesn't 100% support strict domain matching such that a credential for redlorry.acme.com and a credential for bluelorry.acme.com matches on acme.com so they all appear together.

    You might be interested in the autofill behaviours feature: Change where a login is suggested and filled

    Let me know if you have any questions. 🙂

    -Dave

    ref: dev/core/core#27872

  • connrs's avatar
    connrs
    New Contributor
    10 months ago

    I re-read my first sentence and felt I should clarify a little further in case anyone else was unaware: 1Password doesn't 100% support strict domain matching such that a credential for redlorry.acme.com and a credential for bluelorry.acme.com matches on acme.com so they all appear together.

    I'm aware that in recent years, strict URL matching has improved which is a feature that would have been amazing if it existed 10 years ago and if it was exposed in a way that encouraged users to take advantage of it instead of it being buried in a menu against the URL.

    As a result, lots of loose subdomains means a list of credentials too long for the screen to accommodate without becoming inaccessible.