Support scheme upgrade for logins with IP address origins
Categories
(Toolkit :: Password Manager, enhancement, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox70 | --- | affected |
People
(Reporter: vtol, Unassigned)
References
Details
(Whiteboard: [passwords:cross-origin] [passwords:fill-ui])
Attachments
(1 file)
|
3.06 KB,
text/plain
|
Details |
With the current build (da9a6db4b59b15ff3805a97f1a530551acb6b27a ) a login record set for http does not apply for https and vice versa and thus requires to generate a login record for each.
It would seem implausible that the login credentials would be different for each protocol, least I could not come up with a scenario where a server would deploy different credentials depending on whether the ingress traffic is http or https.
Comment 1•6 years ago
|
||
(In reply to vtol from comment #0)
With the current build (da9a6db4b59b15ff3805a97f1a530551acb6b27a ) a login record set for
httpdoes not apply forhttpsand vice versa and thus requires to generate a login record for each.
We implemented fetching of http: logins on https: for the same domain many years ago so please include debug logs of a specific site where you don't see the http: login available over https:?
When filing bugs about the desktop password manager the "Lockwise" name only distracts from the bug issue so please don't include it in your summary, the Password Manager component is enough information to identify the feature you're talking about.
Updated•6 years ago
|
(In reply to Matthew N. [:MattN] (PM me if requests are blocking you) from comment #1)
We implemented fetching of http: logins on https: for the same domain
Perhaps then it is rather about ip addresses only. Got the following LAN entries in Lockwise:
http://[fd30:d64c:1eed:4c3a::12]http://192.168.112.12
And it works on http as expected but does not https -> log attached.
Being on https and
- mouse right click into login field
- menu popup -> fill login -> the record stored for
httpis being displayed
Comment 3•6 years ago
|
||
Hmm… I thought that should work.
Comment 4•4 years ago
|
||
The bug has a release status flag that shows some version of Firefox is affected, thus it will be considered confirmed.
Updated•3 years ago
|
Description
•