Connection Leasing for Hosted Services

• US 20150026777A1
• Filed: 10/07/2014
• Published: 01/22/2015
• Est. Priority Date: 02/16/2012
• Status: Active Grant

• Current Assignee: Citrix Systems, Inc. (Cloud Software Group)
• Original Assignee: Citrix Systems, Inc. (Cloud Software Group)
• Inventors: Bell, Kenneth Malcolm
• Granted Patent: US 9,426,227 B2
• Time in Patent Office: Days
• US Class Current: 726/4
• CPC Class Codes: G06F 9/468 Specific access rights for resources, e.g. using capability register
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• 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/0807 using tickets, e.g. Kerberos cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 67/131 Protocols for games, networked simulations or virtual reality
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/141 Setup of application sessions admission control or resource allocation in data switching networks H04L47/70

Abstract

Aspects herein describe brokering hosted resources in a virtual desktop infrastructure (VDI) using connection leases to reduce demand on connection brokers and to allow hosted services to be maintained even in the event of a broker outage. When a client device desires to connect to a hosted resource (e.g., a hosted desktop or a hosted application), the client device may present a lease token to the session host. The lease token is a self-sustaining package of data from which a session host can determine whether the requesting client device is authorized to access one or more resources hosted by that session host. The lease token may be cryptographically signed to ensure its contents have not been altered, and further that the lease token originated from a trusted source. Lease tokens may be stored independently from a connection broker, thereby still being usable if the connection broker goes offline.

Claims

1. A session host apparatus, comprising:

a processor controlling operations of the session host apparatus; and

memory storing computer readable instructions that, when executed by the processor, cause the session host apparatus to establish a session with a session client by;

receiving a lease token associated with a session client, wherein the lease token is a self-sustaining package of cryptographically signed connection lease data from which the session host apparatus can determine whether the session client device is authorized to access one or more resources hosted by that session host;

determining, based on the lease token, one or more resources, hosted by the session host apparatus, that the session client is authorized to access;

sending connection information to the session client based on the determined resources, after determining that the session client is authorized to access the one or more resources; and

establishing a session with the session client to provide access to the one or more determined resources.

2. The session host apparatus of claim 1, wherein determining comprises checking a lease token revocation database to determine whether the lease token has been revoked.

3. The session host apparatus of claim 1, wherein the lease token comprises a plurality of data fields, each data field defining a different one of:

a lease ID;

a set of one or more client devices;

a set of one or more session hosts; and

a set of one or more resources.

4. The session host apparatus of claim 3, wherein the lease token is signed by a trusted connection broker.

5. The session host apparatus of claim 3, wherein the lease token comprises a plurality of security policy data fields, each security policy data field defining a different one of:

a set of one or more access conditions;

a connection limit;

a maximum idle time; and

a maximum disconnect time.

6. The session host apparatus of claim 5, wherein the access conditions depend on a state of anti-malware software on the session client.

7. A connection broker apparatus, comprising:

a processor controlling operations of the connection broker apparatus; and

memory storing computer readable instructions that, when executed by the processor, cause the connection broker apparatus to administer a connection lease by;

receiving a connection request from a session client;

based on the session client, determining;

one or more session hosts the client is authorized to establish a session with, and

one or more resources the client is authorized to access on said one or more session hosts;

generating a lease token as a data package having a first data field identifying a lease number, a second data field identifying the one or more session hosts, a third data field identifying the one or more resources, and a fourth data field identifying the session client;

cryptographically signing the lease token to verify that the lease token originated at the connection broker apparatus; and

sending the signed lease token to a lease store for storage.

8. The connection broker apparatus of claim 7, wherein sending the lease token includes sending the lease token to the session client for storage on the lease client.

9. The connection broker apparatus of claim 7, wherein sending the lease token includes sending the lease token to a central lease store accessible by the one or more identified session hosts.

10. The connection broker apparatus of claim 7, said instructions further causing the connection broker apparatus to perform:

receiving a request to revoke the lease token; and

revoking the lease token by publishing the lease number to a central revocation list.

11. The connection broker apparatus of claim 7, said instructions further causing the connection broker apparatus to perform:

receiving a request to revoke the lease token; and

revoking the lease token by sending a revocation message to each of the one or more session hosts identified in the lease token.

12. The connection broker apparatus of claim 7, said instructions further causing the connection broker apparatus to perform:

receiving a request to revoke the lease token; and

revoking the lease token by revoking a cryptographic key used to sign the lease token.

13. The connection broker apparatus of claim 7, wherein the lease token further includes a fifth data field identifying a set of one or more access conditions, a sixth data field identifying a connection limit, a seventh data field identifying a maximum idle time, and an eighth data field identifying a maximum disconnect time, wherein each of the fifth through eighth data fields are usable by a session host identified in the second data field to implement a security policy.

14. One or more non-transitory computer readable storage media having a lease token data structure stored thereon, wherein the lease token data structure stores connection lease data, said data structure comprising:

a first data field identifying a lease token identification number;

a second data field identifying one or more client devices;

a third data field identifying one or more session hosts accessible by the one or more client devices;

a fourth data field identifying one or more resources usable by the one or more client devices on the one or more session hosts, wherein each resource is one of a hosted desktop and a hosted application;

a fifth data field identifying a connection limit constraining when the one or more client devices can access the one or more session hosts;

a sixth data field identifying one or more access conditions that must be met by the one or more client devices in order to access the one or more session hosts;

a seventh data field identifying virtual channel information usable by the one or more session hosts to allow or deny access by the one or more clients to one or more virtual channels on the one or more session hosts; and

an eighth data field storing a signature usable by the one or more session hosts to verify that the lease token data structure is unaltered and originated from a trusted connection broker.

15. A method comprising:

receiving a connection request at a connection broker apparatus from a session client;

determining, based on the session client;

one or more session hosts the client is authorized to establish a session with, and

one or more resources the client is authorized to access on said one or more session hosts;

generating a lease token as a self-sustaining data package having a first data field identifying a lease number, a second data field identifying the one or more session hosts, a third data field identifying the one or more resources, and a fourth data field identifying the session client;

cryptographically signing the lease token to verify that the lease token originated at the connection broker apparatus; and

sending the signed lease token to a lease store for storage.

16. The method of claim 15, wherein sending the lease token includes sending the lease token to the session client for storage on the lease client.

17. The method of claim 15, wherein sending the lease token includes sending the lease token to a central lease store accessible by the one or more identified session hosts.

18. The method of claim 15, further comprising revoking the lease token by publishing the lease number to a central revocation list.

19. The method of claim 15, further comprising revoking the lease token by sending a revocation message to each of the one or more session hosts identified in the lease token.

20. The method of claim 15, further comprising revoking the lease token by revoking a cryptographic key used to sign the lease token.

21. The method of claim 15, wherein generating comprises generating the lease token to include a fifth data field identifying a set of one or more access conditions, a sixth data field identifying a connection limit, a seventh data field identifying a maximum idle time, and an eighth data field identifying a maximum disconnect time, wherein each of the fifth through eighth data fields are usable by a session host identified in the second data field to implement a security policy.