3 ms·
I was thinking of writing a spec and implementation on a similar thing a few days ago: Each site would publish a standardized file in a standardized location,
by StavrosK 9y ago
I was thinking of writing a spec and implementation on a similar thing a few days ago:
Each site would publish a standardized file in a standardized location, and/or add a META tag to the file in each page. The file itself would simply contain the URL to the login page and the parameters that should be passed to it, and the way to pass those parameters.
Then, your browser/password manager could simply perform a request in the background, and log you in completely automatically. This solves all the hassle of finding the login form, locating the fields, auto-filling, typing some characters if the change wasn't detected, handling single-page apps, etc.
This could later be extended to signing up automatically. It would make having strong, unique passwords for each site the convenient alternative.
- normalocity 9y agoUnfortunately that requires mass standardization (adopting the spec), which is probably unlikely given that no one standardizes on the registration form to begin with.
- StavrosK 9y agoStandardizing on the form would be much harder. For Django sites, for example, this would be a one-line change (adding the library to Django), and similarly for Node or Rails or most other frameworks. The advantage, where password managers would just log you in transparently on any site, would hopefully be big and visible enough for more and more sites to start implementing this.
- OJFord 9y agoThat would be great! The more likely (as in, one could create it today) implementation would be an extension that could do the GET/POST login, but was oblivious as to required parameters. Then people could contribute the formats expected by different domains. Much less elegant, and only usable by the more technically inclined, but implementable today without explicit support from websites.