Native authentication experience with failover

Patent metadata

Field	Value
Publication number	US-10122697-B2
Application number	US-201715475841-A
Country	US
Kind code	B2
Filing date	Mar 31, 2017
Priority date	Jan 5, 2015
Publication date	Nov 6, 2018
Grant date	Nov 6, 2018

Abstract

Disclosed are various embodiments for providing a native authentication experience with failover. A network service authenticates a first application executed in a computing device in a first instance using one or more authentication factors received via a platform-specific application programming interface that is native to the computing device. After a change to how authentication is performed by the network service, the network service authenticates the first application in a second instance via code-based linking with a second application that is authenticated.

First claim

Therefore, the following is claimed:

1. A non-transitory computer-readable medium embodying a network service executable in at least one computing device, wherein when executed the network service causes the at least one computing device to at least:
authenticate a first application executed in a client computing device in a first instance using at least one authentication factor received via a platform-specific application programming interface that is native to the client computing device;
implement a change to how authentication is performed by the network service after the first application is authenticated in the first instance; and
after the change to how authentication is performed by the network service is implemented, authenticate the first application via code-based linking with a second application that is authenticated.

2. The non-transitory computer-readable medium of claim 1 , wherein the change is a modification to the platform-specific application programming interface.

3. The non-transitory computer-readable medium of claim 1 , wherein the second application is a browser.

4. A system, comprising:
at least one computing device; and
a network service executable in the at least one computing device, wherein when executed the network service causes the at least one computing device to at least:
authenticate a first application executed in a computing device in a first instance using at least one authentication factor received via a platform-specific application programming interface that is native to the computing device; and
after a change to how authentication is performed by the network service, authenticate the first application in a second instance via code-based linking with a second application that is authenticated.

5. The system of claim 4 , wherein the change to how authentication is performed by the network service comprises requiring an authentication factor that was previously not required.

6. The system of claim 4 , wherein the change to how authentication is performed by the network service comprises requiring a hardware configuration of the computing device that was previously not required.

7. The system of claim 4 , wherein the network service provides a first authentication version identifier to the first application in the first instance, and the network service provides a second authentication version identifier to the first application in the second instance.

8. The system of claim 4 , wherein the first application is authenticated in the second instance via code-based linking in response to determining that the first application does not support the change to how authentication is performed.

9. The system of claim 4 , wherein the first application is authenticated in the first instance in response to determining that the first application supports a native authentication approach.

10. The system of claim 4 , wherein authenticating the first application in the second instance via code-based linking further comprises:
providing a code to the first application; and
receiving the code from the second application that is authenticated.

11. The system of claim 10 , wherein authenticating the first application in the second instance via code-based linking further comprises providing a uniform resource locator to the first application in association with the code.

12. The system of claim 10 , wherein the code comprises at least one of: a quick-response (QR) code or a barcode.

13. A method, comprising:
implementing, via at least one of one or more computing devices, a change in how authentication is performed by the one or more computing devices;
receiving, via at least one of one or more computing devices, an authentication request from a first application;
determining, via at least one of the one or more computing devices, that the authentication request is not supported;
providing, via at least one of the one or more computing devices, a code to the first application; and
authenticating, via at least one of the one or more computing devices, the first application in response to receiving the code from a second application that is authenticated.

14. The method of claim 13 , wherein determining that the authentication request is not supported further comprises determining that a secure connection cannot be established with the first application.

15. The method of claim 13 , wherein the authentication request is generated by a platform-specific application programming interface native to a computing device upon which the first application is executed.

16. The method of claim 13 , wherein the first application is executed by a first computing device, and the second application is executed by a second computing device.

17. The method of claim 13 , wherein the authentication request includes at least one authentication factor received via a platform-specific application programming interface.

18. The method of claim 13 , wherein implementing the change in how authentication is performed by the one or more computing devices further comprises removing, via at least one of one or more computing devices, support for the authentication request.

19. The method of claim 13 , wherein implementing the change in how authentication is performed by the one or more computing devices further comprises requiring, via at least one of one or more computing devices, an authentication factor that is not supported by the first application.

20. The method of claim 13 , wherein implementing the change in how authentication is performed by the one or more computing devices further comprises removing, via at least one of one or more computing devices, support for an authentication factor that is required by the first application.

Assignees

• Amazon Tech Inc

Inventors

• Golwalkar Yogesh Vilas
• Joshi Anuj
• Bhimanaik Bharath Kumar
• Millwood Lorne
• Poston Iv Carl Lucian

Classifications

• G06Q30/0609

  Qualifying participants for shopping transactions (payment transaction verification G06Q20/401) · CPC title

• H04L63/10

  for controlling access to devices or network resources · CPC title

• G06F2221/2117

  User registration · CPC title

• H04L9/321

  involving a third party or a trusted authority · CPC title

• H04L9/3234

  involving additional secure or trusted devices, e.g. TPM, smartcard, USB or software token (network architectures or network communication protocols for supporting authentication of entities using an additional device in a packet data network H04L63/0853) · CPC title