1

I have a login credentials for my locally served page saved in Edge:

Screenshot of Edge Password Manager

But each time I access this website, I have to enter it manually always:

Screenshot of locally served webpage

Is there anything that I am missing? Does Edge password manager actually work for locally served, local-network webpage?

Destroy666
  • 12,350
trejder
  • 12,105

3 Answers3

2

Yes, the Edge password manager does work fine for locally-hosted web pages

The browser uses some specific elements and properties in order to tell which text fields are designated for passwords, and whether it should auto-fill them in

If you want to investigate why the password manager isn't activating on that page, there's a list of those requirements and other best practices here: https://web.dev/articles/sign-in-form-best-practices

It doesn't really fix the issue though (unless you're the web developer for that website), so you may be out of luck here

Cpt.Whale
  • 10,914
2

Some websites are coded to prevent pasting. This effectively blocks the password managers I'm aware of, as these primarily use pasting as the method of easily inserting strings into fields on a web form.

You can test this by trying to paste arbitrary text into that field yourself, manually, using either the context (right-click) menu, or CTRL + V. If these do not work, the problem is that this site blocks pasting.

There are already questions dealing with how to force paste to work on a website that tries blocking it. Here's one with a lot of attention and answers that may be worth reviewing: How can I selectively disable paste blockers

Here is a discussion of why some sites may choose to apply this really quite frustrating limitation: https://security.stackexchange.com/questions/2411/why-do-some-sites-block-pasting-into-username-or-password-input-fields

music2myear
  • 49,799
1

Edge, and Chromium-based browsers in general, support saving passwords for any valid hostname, at least on HTTP(S) protocol.

Firstly, ensure there are no redirects that might mess with hostname-based matching. It looks like some router configuration page, which matches the IP, so there should be no issue like that. I also doubt it's blocked in any way.

The most likely reason is that the field doesn't even have name="password" attribute, which is the bare minimum for any sort of autofill. If that's the case, you could try adding a Tampermonkey script that modifies the field to add e.g. autocomplete="current-password" attribute to it, which is prioritized. You might need to use MutationObserver loaded at the start to ensure it's added as soon as possible and detected by Edge.

Destroy666
  • 12,350