Now it works just fine. So I guess it wasn't because of a Chrome update after all. I guess I must've been using the IP address before. So what does this mean for the future of basic authentication in lastpass?
Yeah, the only way I see it working in the past is if you were using a hostname with a "." in it, an IP address, or had Chrome set to English.
As for HTTP authentication support in general, Firefox is the only browser whose extensions API allows us to directly fill data into an HTTP authentication window. The methods we're using for Internet Explorer and Chrome are really hacks, when it comes down to it. Thus, they're often susceptible to breaking when changes are made to the browsers.
I am wondering if the LP 2.55 (binary true) version is currently working with Chrome v29.0.1547,57m (Windows) for BasicAuth logins? Because I tried everything but I can't get it to work. Here's what my Tools>About says:
The Chrome team has provided a workaround for now. Go to:
find "Views Textfield", and change it to "Disabled". Restart Chrome and your dialogs should be fillable again.
This worked for me, glad I can get LP working again as I was about to change back to Firefox. It would be good if this fix could be made as a sticky because I'm sure there are a lot of people having this problem at the moment.
It currently works on the latest Chrome Canary build, and will presumably work on the Chrome dev channel next time it's released. It should in theory support Chrome 30 (currently in beta) if this patch ever makes it there, but without a working build, it's hard to tell for sure.
Hi there Since Chrome v30 is now out in the official channel (just updated) - can you guys please fast-track this fix into the release version of the LastPass + binary extension? Been a long time coming on this fix! thanks