Browser based identity with multiple login
US-2015288522-A1 · Oct 8, 2015 · US
US2018019984A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2018019984-A1 |
| Application number | US-201715678664-A |
| Country | US |
| Kind code | A1 |
| Filing date | Aug 16, 2017 |
| Priority date | Mar 31, 2014 |
| Publication date | Jan 18, 2018 |
| Grant date | — |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Disclosed is an approach for enabling a user to login to a site without needing to manually type in credentials. A method includes receiving, from a site, at a browser and via a browser credential management application programming interface that defines a protocol for communicating data between the site and the browser for enabling a user to login to the site, a request associated with a login credential required for the site, retrieving, based on the request, user data and transmitting, to the site, from the browser and via the browser credential management application programming interface, a response to the request. The response can include such login data as username and password.
Opening claim text (preview).
We claim: 1 . A method comprising: receiving, from a site, at a browser and via a browser credential management application programming interface that defines a protocol for communicating data between the site and the browser for enabling a user to login to the site, a request for authorized user data for logging into the site; retrieving, based on the request, the authorized user data; and transmitting, to the site, from the browser and via the browser credential management application programming interface, the authorized user data for use in logging into the site. 2 . The method of claim 1 , wherein the authorized user data comprises at least one of a user name or a password. 3 . The method of claim 2 , wherein at least one of the authorized user data, the user name and the password is stored with the browser. 4 . The method of claim 1 , wherein the authorized user data indicates that a network-based entity will provide credential data for logging into the site. 5 . The method of claim 4 , wherein the site accesses, via a second application programming interface between the site and a network based entity, the credential data for the user to login to the site. 6 . The method of claim 1 , wherein the authorized user data comprises a username and a password, wherein the username and the password are stored with the browser. 7 . The method of claim 1 , further comprising: receiving a change in a user credential via the browser credential management application programming interface. 8 . A system comprising: a processor; and a computer-readable storage device storing instructions which, when executed by the processor, cause the processor to perform operations comprising: receiving, from a site, at a browser and via a browser credential management application programming interface that defines a protocol for communicating data between the site and the browser for enabling a user to login to the site, a request for authorized user data for logging into the site; retrieving, based on the request, the authorized user data; and transmitting, to the site, from the browser and via the browser credential management application programming interface, the authorized user data for use in logging into the site. 9 . The system of claim 8 , wherein the authorized user data comprises at least one of a user name or a password. 10 . The system of claim 9 , wherein at least one of the authorized user data, the user name and the password is stored with the browser. 11 . The system of claim 8 , wherein the authorized user data indicates that a network-based entity will provide credential data for logging into the site. 12 . The system of claim 11 , wherein the site accesses, via a second application programming interface between the site and a network based entity, the credential data for the user to login to the site. 13 . The system of claim 8 , wherein the authorized user data comprises a user name and a password, wherein the user name and the password are stored with the browser. 14 . The system of claim 8 , wherein the computer-readable storage device stores additional instructions which, when executed by the processor, cause the processor to perform operations further comprising: receiving a change in a user credential via the browser credential management application programming interface. 15 . A method comprising: transmitting, from a site, to a browser and via a browser credential management application programming interface that defines a protocol for communicating data between the site and the browser for enabling a user to login to the site, a request for authorized user data for use in logging into the site; and receiving, at the site, from the browser and via the browser credential management application programming interface, the authorized user data in response to the request. 16 . The method of claim 15 , wherein the authorized user data comprises at least one of a user name or a password. 17 . The method of claim 16 , wherein at least one of the authorized user data, the user name and the password is stored with the browser. 18 . The method of claim 15 , wherein the authorized user data indicates that a network-based entity will provide credential data for logging into the site. 19 . The method of claim 15 , wherein the authorized user data comprises a username and a password, wherein the username and the password are stored with the browser. 20 . The method of claim 15 , further comprising: requesting, via a second application programming interface between the site and a network based entity, the authorized user data for the user to login to the site.
Managing shopping lists, e.g. compiling or processing purchase lists (shipping orders G06Q10/083; order filling G06Q10/087) · CPC title
Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists · CPC title
utilising user interfaces specially adapted for shopping · CPC title
replenishment orders; recurring orders · CPC title
by formulating product or service queries, e.g. using keywords or predefined options · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.