LEVERAGING A PERSISTENT CONNECTION TO ACCESS A SECURED SERVICE

• US 20150156187A1
• Filed: 12/30/2014
• Published: 06/04/2015
• Est. Priority Date: 04/11/2001
• Status: Active Grant

• Current Assignee: Meta Platforms, Inc. (f/k/a Facebook, Inc.)
• Original Assignee: Meta Platforms, Inc. (f/k/a Facebook, Inc.)
• Inventors: Hirsh, Robert Bruce
• Granted Patent: US 9,197,626 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/0815 providing single-sign-on or federations
• 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/0884 by delegation of authentication, e.g. a proxy authenticates an entity to be authenticated on behalf of this entity vis-à-vis an authentication entity
• CPC Class Codes: H04L 67/55 Push-based network services

Abstract

Leveraging a persistent connection to provide a client access to a secured service may include establishing a persistent connection with a client in response to a first request from the client, and brokering a connection between the client and a secured service based on a second request from the client by leveraging the persistent connection with the client. The brokering may occur before the client attempts to connect to the secured service directly and the connection may be established between the client and the secured service without provision by the client of authentication information duplicative or additional to authentication information provided by the client to establish the persistent connection.

Claims

1. A method comprising:

establishing, using at least one processor, a connection with an intermediary system;

sending, to the intermediary system, a request for authorization to access a secured service;

receiving, from the intermediary system, authorization information for accessing the secured service;

accessing, independent of the connection with the intermediary system, the secured service using the authorization information; and

synchronizing local data with remote data stored by the secured service.

2. The method of claim 1, wherein the authorization information comprises constraint information.

3. The method of claim 2, wherein the constraint information includes at least one of an indication of a number of uses for which the authorization information may be used, an indication of a time when the authorization information was determined, an indication of a window of time in which the authorization information may be used, or information indicative of an identity of the client for whom the authorization information was determined.

4. The method of claim 2, wherein the received authorization information comprises constraint information used to enable a direct connection between the client and the secured service.

5. The method of claim 2, further comprising:

providing keystone authentication information to the intermediary system; and

authenticating with the intermediary system based on the keystone authentication information.

6. The method of claim 2, wherein the secured service comprises at least one of a calendar synchronization service or a task list synchronization service.

7. The method of claim 2, wherein local data and remote data comprise at least a portion of a calendar or a task list.

8. An apparatus comprising:

one or more processors; and

one or more memories operatively coupled to at least one of the one or more processors and having instructions stored thereon that, when executed by at least one of the one or more processors, cause the apparatus to;

establish a connection with an intermediary system;

send to the intermediary system, a request for authorization to access a secured service;

receive from the intermediary system, authorization information for accessing the secured service;

access, independent of the connection with the intermediary system, the secured service using the authorization information; and

synchronize local data with remote data stored by the secured service.

9. The apparatus of claim 8, wherein the authorization information comprises constraint information.

10. The apparatus of claim 9, wherein the constraint information comprises at least one of an indication of a number of uses for which the authorization information may be used, an indication of a time when the authorization information was determined, an indication of a window of time in which the authorization information may be used, or information indicative of an identity of the client for whom the authorization information was determined.

11. The apparatus of claim 9, wherein the constraint information is used to enable a direct connection between the client and the secured service.

12. The apparatus of claim 8, wherein the instructions, when executed by at least one of the one or more processors, further cause the apparatus to:

provide keystone authentication information to the intermediary system; and

authenticate with the intermediary system based on the keystone authentication information.

13. The apparatus of claim 8, wherein the secured service comprises at least one of a calendar synchronization service or a task list synchronization service.

14. The apparatus of claim 8, wherein local data and remote data comprise at least a portion of a calendar or a task list.

15. At least one non-transitory computer-readable medium storing computer-readable instructions that, when executed by one or more computing devices, cause at least one of the one or more computing devices to:

establish a connection with an intermediary system;

send to the intermediary system, a request for authorization to access a secured service;

receive from the intermediary system, authorization information for accessing the secured service;

access, independent of the connection with the intermediary system, the secured service using the authorization information; and

synchronize local data with remote data stored by the secured service.

16. The computer-implemented method of claim 15, wherein the authorization information comprises constraint information.

17. The non-transitory computer-readable medium of claim 16, wherein the constraint information comprises at least one of an indication of a number of uses for which the authorization information may be used, an indication of a time when the authorization information was determined, an indication of a window of time in which the authorization information may be used, or information indicative of an identity of the client for whom the authorization information was determined.

18. The non-transitory computer-readable medium of claim 16, wherein the constraint information is usable to enable a direct connection between the client and the secured service.

19. The non-transitory computer-readable medium of claim 16, wherein the secured service comprises at least one of a calendar synchronization service or a task list synchronization service.

20. The non-transitory computer-readable medium of claim 16, wherein local data and remote data comprise at least a portion of a calendar or a task list.