Authentication manager

US9369460B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9369460-B2
Application numberUS-201414323779-A
CountryUS
Kind codeB2
Filing dateJul 3, 2014
Priority dateAug 12, 2009
Publication dateJun 14, 2016
Grant dateJun 14, 2016

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Disclosed are various embodiments for an authentication manager. The authentication manager performs a certificate validation for a network site. If the certificate validation is successful, the authentication manager automatically provides a security credential to the network site.

First claim

Opening claim text (preview).

Therefore, the following is claimed: 1. A non-transitory computer-readable medium embodying an authentication manager executable via a client computing device, wherein when executed the authentication manager causes the client computing device to at least: in response to receiving data encoding a secure certificate from a network site, perform a trusted certificate validation on the secure certificate; perform a reverse domain name system (DNS) lookup on an internet protocol (IP) address associated with the network site; perform a comparison between a domain name resulting from the reverse DNS lookup and a stored domain name, the stored domain name being previously received from a trusted certificate and stored in a data store accessible to the client computing device; and automatically send data encoding a security credential to the network site based at least in part on the comparison when the trusted certificate validation is successful. 2. The non-transitory computer-readable medium of claim 1 , wherein when executed the authentication manager further causes the client computing device to at least that automatically generate the security credential according to a security credential specification. 3. The non-transitory computer-readable medium of claim 1 , wherein when executed the authentication manager further causes the client computing device to at least refrain from automatically sending the data encoding the security credential to the network site when the trusted certificate validation is unsuccessful. 4. The non-transitory computer-readable medium of claim 1 , wherein when executed the authentication manager further causes the client computing device to at least determine whether the secure certificate currently provided by the network site matches the trusted certificate previously provided by the network site. 5. A system, comprising: a client computing device; and an authentication manager executable in the client computing device, wherein when executed the authentication manager causes the client computing device to at least: in response to receiving data encoding a secure certificate from a network site, perform a certificate validation on the secure certificate; perform a reverse domain name system (DNS) lookup on an internet protocol (IP) address associated with the network site; perform a comparison between a domain name resulting from the reverse DNS lookup and a stored domain name, the stored domain name being previously received from a trusted certificate and stored in a data store accessible to the client computing device; and automatically send data encoding a security credential to the network site based at least in part on the comparison in response to determining that the certificate validation is successful. 6. The system of claim 5 , wherein when executed the authentication manager further causes the client computing device to at least reauthenticate a user at the client computing device in response to determining that the certificate validation is unsuccessful. 7. The system of claim 5 , wherein when executed the authentication manager further causes the client computing device to at least automatically send the data encoding the security credential to the network site further based at least in part on comparing a stored uniform resource locator associated with the network site with a content of a browser address bar that is rendering a network page of the network site. 8. The system of claim 5 , wherein when executed the authentication manager further causes the client computing device to at least automatically send the data encoding the security credential to the network site further based at least in part on comparing the stored domain name with a content of a protocol header sent by the network site. 9. The system of claim 5 , wherein when executed the authentication manager further causes the client computing device to at least: compare the secure certificate with the trusted certificate from the network site in performing the certificate validation, the trusted certificate being stored upon the client computing device. 10. The system of claim 9 , wherein when executed the authentication manager further causes the client computing device to at least compare a domain name of the secure certificate with the stored domain name. 11. The system of claim 5 , wherein when executed the authentication manager further causes the client computing device to at least: in response to receiving a configuration file including a security credential specification from the network site, extract a maximum credential length and a character set from the security credential specification; and wherein the security credential is automatically generated based at least in part on the maximum credential length and the character set allowed by the security credential specification. 12. The system of claim 5 , wherein the stored domain name is stored in association with the security credential. 13. A method, comprising: receiving, via an authentication manager executed by a client, data encoding a certificate from a network site; performing, via the authentication manager executed by the client, a validation upon the certificate; performing, via the authentication manager executed by the client, a reverse domain name system (DNS) lookup on an internet protocol (IP) address associated with the network site; performing, via the authentication manager executed by the client, a comparison between a domain name resulting from the reverse DNS lookup and a stored domain name, the stored domain name being previously received from a trusted certificate and stored in a data store accessible to the client; and in response to determining that the validation is successful, automatically sending, via the authentication manager executed by the client, data encoding a security credential to the network site based at least in part on the comparison. 14. The method of claim 13 , further comprising automatically generating, via the authentication manager executed by the client, the security credential. 15. The method of claim 14 , further comprising: receiving, via the authentication manager executed by the client, a configuration file including a security credential specification from the network site; extracting, via the authentication manager executed by the client, a maximum credential length and a character set from the security credential specification; and wherein the security credential is automatically generated based at least in part on the maximum credential length and the character set allowed by the security credential specification. 16. The method of claim 13 , further comprising, in response to determining that the validation is unsuccessful, refraining from automatically sending, via the authentication manager executed by the client, the data encoding the security credential to the network site. 17. The method of claim 13 , further comprising determining, via the authentication manager executed by the client, whether a user at the client has provided a correct master security credential, wherein the data encoding the security credential is automatically sent further based at least in part on determining that the user has provided the correct master security credential. 18. The method of claim 13 , further comprising determining, via the authentication manager executed by the client, whether a particular portable data store is present in the client, the particular portable data store being configured to store the security credential, wh

Assignees

Inventors

Classifications

  • for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32) · CPC title

  • User authentication · CPC title

  • H04L63/083Primary

    using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226) · CPC title

  • using certificates (cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263) · CPC title

  • Authenticating web pages, e.g. with suspicious links · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9369460B2 cover?
Disclosed are various embodiments for an authentication manager. The authentication manager performs a certificate validation for a network site. If the certificate validation is successful, the authentication manager automatically provides a security credential to the network site.
Who is the assignee on this patent?
Amazon Tech Inc
What technology area does this patent fall under?
Primary CPC classification H04L63/083. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Jun 14 2016 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).