Multiple data store authentication

• US 9,578,027 B1
• Filed: 05/15/2016
• Issued: 02/21/2017
• Est. Priority Date: 04/21/2005
• Status: Active Grant

• Current Assignee: Seven Networks LLC (SoftBank Group Corp.)
• Original Assignee: Seven Networks LLC (SoftBank Group Corp.)
• Inventors: Sutaria, Jay, Gustafson, Brian Daniel, van Gent, Robert Paul, Lin, Ruth, Merriwether, David, Sawhney, Parvinder
• Primary Examiner(s): Mehedi, Morshed
• Application Number:
  US15/155,061
• Time in Patent Office: 282 Days
• US Class Current: 1/1
• CPC Class Codes: G06F 21/44 Program or device authentication
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 63/0876 based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04W 12/06 Authentication
• CPC Class Codes: H04W 12/069 using certificates or pre-shared keys
• CPC Class Codes: H04W 12/08 Access security

Abstract

System and methods for authenticating access to multiple data stores are disclosed. The system may include a server coupled to a network, a client device in communication with the server via the network and a plurality of data stores. The server may authenticate access to the data stores and forward information from those stores to the client device. An exemplary authentication method receives a request for access to data. Information concerning access to that data is stored and associated with an identifier assigned to a client device. If the identifier is found to correspond to the stored information during a future request for access to the store, access to that store is granted.

Claims

1. A server communicatively coupled to a network and one or more data stores, the server comprising:

a processor; and

a memory, wherein the server is configured to;

receive, from a client device, a unique identifier for the client device, wherein the unique identifier is transmitted between the client device and the server as part of an initial communication, wherein the unique identifier is also used in a subsequent communication;

store the unique identifier for the client device;

identify the client device using the stored unique identifier;

receive registration information from the client device;

store the registration information;

associate the stored registration information with the unique identifier of the client device;

receive, via a communication with the client device, a request for the client device to receive information from the one or more data stores, wherein the request includes the unique identifier;

configure a service to access the one or more data stores on behalf of the client device using the stored registration information; and

forward the requested information from the one or more data stores to the client device based on the unique identifier that is included within the request.

2. The server of claim 1, wherein the one or more data stores are associated with an electronic mail service provider.

3. The server of claim 1, wherein the client device is one of a cellular telephone, personal digital assistant, or personal computer.

4. The server of claim 1, wherein the server authenticates the client device prior to the server authenticating access to the one or more data stores.

5. The server of claim 1, wherein the server authenticates a user of the client device prior to the server authenticating access to the one or more data stores.

6. The server of claim 4, wherein the authentication of the client device includes the use of the unique identifier.

7. The server of claim 4, wherein the unique identifier is a token, the token comprising a unique string of data.

8. The server of claim 5, wherein the authentication of the user of the client device includes the use of a user name.

9. The server of claim 8, wherein the authentication of the user of the client device includes the use of the user name in combination with a password and wherein authenticating access to the one or more data stores also includes the use of the user name in combination with the password.

10. The server of claim 1, wherein, upon receiving the information from the data store, the server is further configured to:

use one of the stored registration information or an internal identifier associated with the stored registration information to determine the unique identifier that should receive the information from the data store; and

wherein forwarding the information from the one or more data stores to the client device includes providing any data queued for the determined identifier when the client device connects and presents the unique identifier.

11. The server of claim 1, wherein, upon receiving the information from the data store, the server is further configured to:

store the information from the data store for accounts identified by the stored registration information or an internal identifier associated with the stored registration information; and

retrieve the information from the data store for the accounts identified by the stored registration information or the internal identifier when the client device connects and presents the unique identifier.

12. A computing device for authenticating access to one or more data stores, comprising:

a communications interface that exchanges registration information and identification information over a network;

a memory and a processor, wherein the computing device is configured to;

receive, from a client device, a unique identifier for the client device, wherein the unique identifier is transmitted between the client device and the computing device as part of an initial communication, wherein the unique identifier is also used in a subsequent communication;

store the unique identifier for the client device;

identify the client device using the stored unique identifier;

receive registration information from the client device;

store the registration information; and

associate the stored registration information with the unique identifier of the client device; and

wherein the computing device is further configured to;

receive, via a communication with the client device, a request for the client device to receive information from the one or more data stores, wherein the request includes the unique identifier;

configure a service to access the one or more data stores on behalf of the client device using the stored registration information and/or the additional registration information, wherein the client device need not make contact with the one or more data stores for the purpose of authentication; and

forward the requested information from the one or more data stores to the client device based on the unique identifier that is included within the request.

13. The computing device of claim 12, wherein the client device can provide the unique identifier for verification purposes when the client device subsequently communicates with the computing device.

14. The computing device of claim 12, wherein the communications interface receives information from the one or more data stores following authentication of the client device or user thereof.

15. The computing device of claim 14, wherein the communication interface forwards the information received from the one or more data stores to the client device.

16. The computing device of claim 12, wherein the unique identifier is a token comprising a unique string of data.

17. The computing device of claim 12, wherein the unique identifier is a telephone number.

18. The computing device of claim 12, wherein, upon receiving the information from the data store, the computing device is further configured to:

use one of the stored registration information or an internal identifier associated with the stored registration information to determine the unique identifier that should receive the information from the data store, and

wherein forwarding the information from the one or more data stores to the client device includes providing any data queued for the determined identifier when the client device connects and presents the unique identifier.

19. The computing device of claim 12, wherein, upon receiving the information from the data store, the computing device is further configured to:

store the information from the data store for accounts identified by the stored registration information or an internal identifier associated with the stored registration information; and

retrieve the information from the data store for the accounts identified by the stored registration information or the internal identifier when the client device connects and presents the unique identifier.

20. A method for authenticating access to one or more data stores, comprising:

receiving, at a server from a client device, a unique identifier for the client device, wherein the unique identifier is transmitted between the client device and the server as part of an initial communication, wherein the unique identifier is used in a subsequent communication;

storing the unique identifier for the client device;

identifying the client device using the stored unique identifier;

receiving, at the server, registration information from the client device;

storing the registration information;

associating the stored registration information with the unique identifier of the client device;

receiving a request from the client device for the client device to receive information from the one or more data stores;

using the stored registration information to configure a service to access the one or more data stores on behalf of the client device; and

forwarding the requested access for information from the one or more data stores to the client device based on the unique identifier that is included within the request.

21. The method of claim 20, wherein the client device can present the unique identifier in a subsequent communication with the server.

22. The method of claim 20, further comprising querying the user to verify that the collected registration information associated with the unique identifier is correct.

23. The method of claim 22, wherein the user is queried to verify the accuracy of the collected registration information according to a length of time between registering the user for the requested service and when the collected information was collected.

24. The method of claim 22, further comprising querying the user for a password to complete the registration for the requested service.

25. The method of claim 20, further comprising, upon receiving the information from the data store:

using one of the stored registration information or an internal identifier associated with the stored registration information to determine the unique identifier that should receive the information from the data store; and

wherein forwarding the information from the one or more data stores to the client device includes providing any data queued for the determined identifier when the client device connects and presents the unique identifier.

26. The method of claim 20, further comprising, upon receiving the information from the data store:

storing the information from the data store for accounts identified by the stored registration information or an internal identifier associated with the stored registration information; and

retrieving the information from the data store for the accounts identified by the stored registration information or the internal identifier when the client device connects and presents the unique identifier.