Systems and methods for signaling an attack on contactless cards
US-12081582-B2 · Sep 3, 2024 · US
US9608974B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9608974-B2 |
| Application number | US-201514629372-A |
| Country | US |
| Kind code | B2 |
| Filing date | Feb 23, 2015 |
| Priority date | Mar 14, 2013 |
| Publication date | Mar 28, 2017 |
| Grant date | Mar 28, 2017 |
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.
Approaches are described for automatically generating new security credentials, such as security tokens, which can involve automatically re-authenticating a user (or client device) using a previous security token issued to that user (or device). The re-authentication can happen without any knowledge and/or action on the part of the user. The re-authentication mechanism can invalidate and/or keep track of the previous security token, such that when a subsequent request is received that includes the previous security token, the new security token can be invalidated, and the user caused to re-authenticate, as receiving more than one request with the previous security token can be indicative that the user's token might have been stolen.
Opening claim text (preview).
What is claimed is: 1. A computer-implemented method, comprising: under control of one or more computer systems configured with executable instructions, receiving an authentication request from an account associated with a computing device registered with a provider environment, the authentication request including a first token; determining that the first token is expired; determining that the first token matches a second token that is stored in persistent storage; determining that the second token is outside of a renewal window for the computing device; issuing a new token to be used by the computing device; storing the new token in the persistent storage as an unconfirmed new token; receiving a confirmation of the unconfirmed new token; and storing data indicating the unconfirmed new token is a confirmed new token. 2. The computer-implemented method of claim 1 further comprising: determining that the account associated with the computing device is no longer active with the provider environment; denying the authentication request; and deleting all tokens associated with the computing device registered with the provider environment. 3. The computer-implemented method of claim 1 further comprising: determining that the account associated with the computing device is no longer active with the provider environment; denying the authentication request; de-registering the computing device from the provider environment; and returning an indication of a failed authentication to the computing device. 4. A computer-implemented method, comprising: under control of one or more computer systems configured with executable instructions, receiving an authentication request from an account associated with a computing device used in a provider environment, the authentication request including a first token; determining that the first token is expired; determining that the first token matches a second token that is stored in persistent storage; determining that the second token is within a renewal window for the computing device; determining that the account associated with the computing device is an active account; issuing a new token to be used by the computing device in the provider environment; storing the new token in the persistent storage as an unconfirmed new token; receiving a confirmation of the unconfirmed new token; and storing data indicating the unconfirmed new token is a confirmed new token. 5. The computer-implemented method of claim 4 further comprising: storing data indicating the new token is the unconfirmed token; and sending the new token to the computing device. 6. The computer-implemented method of claim 4 further comprising: determining that the account associated with the computing device is no longer active with the provider environment; deleting all tokens associated with the computing device; and de-registering the computing device from the provider environment. 7. The computer-implemented method of claim 4 further comprising: determining that a third token is stored in persistent storage and has not been confirmed by the computing device; and determining that the third token has expired. 8. The computer-implemented method of claim 4 , further comprising: subsequent to determining that the second token is within a renewal window for the computing device, determining that the second token is outside the renewal window for the computing device; and denying the authentication request. 9. A computing system, comprising: at least one processor; and memory including instructions that, when executed by the at least one processor, cause the computing system to: receive an authentication request from an account associated with a computing device registered with a provider environment, the authentication request including a first token; determine that the first token is expired; determine that the first token matches a second token that is stored in persistent storage; and determine that the second token is outside of a renewal window for the computing device; issuing a new token to be used by the computing device; storing the new token in the persistent storage as an unconfirmed new token; receive a confirmation of the unconfirmed new token; and store data indicating the unconfirmed new token is a confirmed new token. 10. The computing system of claim 9 wherein the instructions, when executed, further cause the computing system to: determine that the account associated with the computing device is no longer active with the provider environment; delete all tokens associated with the computing device registered to the provider environment; de-register the computing device from the provider environment; and return an indication of faded authentication to the computing device. 11. The computing system of claim 9 wherein the instructions, when executed, cause the computing device to: determine that the second token is within the renewal window; and authorize the authentication request. 12. The computing system of claim 9 wherein the instructions, when executed, further cause the computing system to: determine that an account associated with the computing device is an active account. 13. The computing system of claim 9 wherein the instructions, when executed, further cause the computing system to: determine that the account associated with the computing device is not an active account with the provider environment; delete all tokens associated with the computing device; and de-register the computing device from the provider environment.
using time-dependent-passwords, e.g. periodically changing passwords · CPC title
for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.