Desktop application fulfillment platform with multiple authentication mechanisms

US9985953B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9985953-B2
Application numberUS-201414537789-A
CountryUS
Kind codeB2
Filing dateNov 10, 2014
Priority dateNov 10, 2014
Publication dateMay 29, 2018
Grant dateMay 29, 2018

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

A service provider system may include an application fulfillment platform that delivers desktop applications to desktops on physical computing devices or virtual desktop instances. A computing resource instance may be registered with the platform, which generates a unique identifier and a security token for the computing resource instance using multiple authentication mechanisms. An end user of a customer organization may be registered with the platform, which generates a unique identifier and a security token for the end user using multiple authentication mechanisms. An application delivery agent may submit service requests to the platform on behalf of itself or the given user. The identity and security credentials included in the requests may be dependent on the request type and the entities on whose behalf they are submitted. A proxy service on the platform may receive the requests and validate the credentials, then dispatch the requests to other services on the platform.

First claim

Opening claim text (preview).

What is claimed is: 1. A system, comprising: a plurality of computing nodes that collectively provide virtual computing services to one or more clients of a service provider, each of the computing nodes comprising at least one processor and a memory; and a virtualized computing resource instance executing on one of the computing nodes; wherein the virtualized computing resource instance implements a virtual desktop instance on behalf of a given end user that receives services from the service provider, and wherein an application delivery agent is installed on the virtual desktop instance; wherein one or more of the plurality of computing nodes implement an application fulfillment platform; wherein the application fulfillment platform is configured to: receive, from the application delivery agent, a request to register the virtual desktop instance with the application fulfillment platform as a device, wherein the request includes a device identity ticket; in response to the request to register the virtual desktop instance: validate the device identity ticket; generate a security token for the device; and return the security token for the device to the application delivery agent; receive, from the application delivery agent, a request to register the given end user with the application fulfillment platform, wherein the request includes a user identity ticket received from an active directory service; in response to the request to register the given end user: validate the user identity ticket; generate a security token for the given end user; and return the security token for the given end user to the application delivery agent; and receive, from the application delivery agent, a request for service, wherein the request for service includes the security token for the device or the security token for the given end user, and wherein the security token included in the request for service is dependent on the type of the service request or the entity on whose behalf the service request was submitted by the application delivery agent. 2. The system of claim 1 , wherein the request was submitted by the application delivery agent on behalf of the application delivery agent; and wherein the request for service comprises an identifier of the device and the security token for the device. 3. The system of claim 1 , wherein the request was submitted by the application delivery agent on behalf of the given end user; and wherein the request for service comprises an identifier of the given end user and the security token for the given end user. 4. The system of claim 1 , wherein the application fulfillment platform comprises a plurality of control plane services, including a proxy service; wherein one or more of the request to register the virtual desktop instance, the request to register the end user, or the request for service is received by a proxy service; and wherein in response to receiving the request to register the virtual desktop instance, the request to register the end user, or the request for service, the proxy service is configured to: validate a security token included in the request; and dispatch the request to another one of the control plane services. 5. The system of claim 4 , wherein the application fulfillment platform comprises an outbound queue from which the application delivery agent can retrieve notifications; wherein the other one of the control plane services is configured to: receive the dispatched request for service; process the dispatched request for service; and return a response for the dispatched request for service to the application delivery agent, wherein to return the response, the other one of the control plane services places a notification in the outbound queue for retrieval by the application delivery agent. 6. A method, comprising: performing, by one or more computers that implement an application fulfillment platform on resources of a service provider: receiving a service request from an application delivery agent that is installed on a computing resource instance of a given user in an organization that receives services from the service provider, wherein the service request comprises a security credential for the computing resource instance or a security credential for the given user; and in response to receiving the service request, validating a particular identity resource of a plurality of different identity resources using two or more authentication mechanisms, wherein the particular identity resource being validated is based on whether the service request was submitted by the application delivery agent on behalf of the computing resource instance or was submitted by the application delivery agent on behalf of the given user, and wherein individual ones of the different identity resources comprise: an identity of the computing resource instance and a security credential for the computing resource instance, or an identity of the given user and a security credential for the given user; and in response to validating the identity and the security credential for the computing resource instance of the given user or for the given user, processing the service request. 7. The method of claim 6 , further comprising, prior to said receiving: generating the security credential for the computing resource instance of the given user; or generating the security credential for the given user. 8. The method of claim 7 , wherein the method further comprises, prior to receiving the service request, receiving a request to register the computing resource instance with the application fulfillment service platform; and wherein said generating the security credential for the computing resource instance of the given user is performed in response to receiving the request to register the computing resource instance with the application fulfillment service platform. 9. The method of claim 7 , wherein the method further comprises, prior to receiving the service request, receiving a request to register the given user with the application fulfillment service platform or an indication that the given user has logged into the computing resource instance; and wherein said generating the security credential for the given user is performed in response to receiving the request to register the given user with the application fulfillment service platform or the indication that the given user has logged into the computing resource instance. 10. The method of claim 7 , wherein at least one of said generating the security credential for the computing resource instance of the given user or said generating the security credential for the given user comprises generating a temporary security token that expires after a pre-determined period of time; and wherein the method further comprises renewing the temporary security token in response to the temporary security token expiring. 11. The method of claim 7 , wherein at least one of said generating the security credential for the computing resource instance of the given user or said generating the security credential for the given user comprises: receiving a security credential or unique resource identifier for the computing resource instance of the given user or for the given user that is of a different type than that of the security credential and that is not recognized by one or more control plane services implemented by the application fulfillment platform; reformatting the security credential or unique resource identifier for the computing resource instance of the given user or for the given user that is of the different type; and exchanging the reformatted security credential or uniqu

Assignees

Inventors

Classifications

  • for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32) · CPC title

  • for accessing specific resources, e.g. using Kerberos tickets · CPC title

  • wherein the data content is protected, e.g. by encrypting or encapsulating the payload · CPC title

  • using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213) · CPC title

  • for controlling access to devices or network resources · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9985953B2 cover?
A service provider system may include an application fulfillment platform that delivers desktop applications to desktops on physical computing devices or virtual desktop instances. A computing resource instance may be registered with the platform, which generates a unique identifier and a security token for the computing resource instance using multiple authentication mechanisms. An end user of…
Who is the assignee on this patent?
Amazon Tech Inc
What technology area does this patent fall under?
Primary CPC classification H04L63/0428. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue May 29 2018 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 4 related publications on this page (citations in our corpus or others sharing the same primary CPC).