Patent Description:
For instance, a platform may have partners who accept credit cards or sensitive information from their customers. A customer's sensitive information (e.g. credit card or personal identification data) is provided to the API of a service through a partner provider (e.g. a Payment Card Industry Data Security Standard (PCI DSS) compliant vault or Health Insurance Portability and Accountability Act (HIPPA) compliant service) that maintains the sensitive information.

However, PCI DSS or HIPPA compliance can be complex and expensive to implement. Frequently, PCI DSS or HIPPA compliance is delegated to a compliant partner, which then participates in a transaction (e.g. a purchase or data transfer). This approach involves customers or users sharing their OAuth tokens with these compliant partners in order to perform a transaction. Sharing a token introduces security risk and prevents auditing the use of the token to accurately identify an entity participating in a transaction.

Typically, sharing an OAuth token involves the partner impersonating another entity, such as the customer. The impersonating entity appears to the API to be the customer because the token identifies only the customer. Sharing the token creates a security risk. Impersonation of the customer prevents the token from being used to identify the impersonating entity as participating in the transaction and, therefore, limits the auditability of the transaction.

<NPL> describes API-to API scenarios involving OAuth token exchange. Accordingly, the simplest thing to do is have the API gateway re-use the access token it receives and pass it on to the next API. Another approach is to create a new grant type that can be used to exchange access tokens used to access API1 for a new access token that can call API2 while still acting on the user's behalf.

The claimed invention relates to a method, a system and a computer storage medium, as set out in the appended claims.

The disclosed technology is directed toward advanced security networking protocol extensions and APIs that can extend composite tokens described in a recent OAuth proposal for delegating permissions from a subject entity to an actor entity to create trust stacks that provide for complex delegations of permissions that can be audited and verified.

In certain simplified examples of the disclosed technologies, methods, systems or computer readable media for trust or authorization delegation for extension of OAuth multiple actor delegation in accordance with the disclosed technology involve receiving a first authorization request from a subject client and responding to the first authorization by sending a first token having a first set of permissions to the subject client. The disclosed technology also involves receiving a second authorization request from a first partner actor, the second authorization request including the first token and responding to the second authorization request by linking the first partner actor to the subject client in a trust stack pertaining to the subject client and sending a second token to the first actor partner with a second set of permissions, where the second token comprises a first complex token that identifies the subject client and the first partner actor. The technology further involves receiving a third authorization request from a second partner actor, the third authorization request including the second token and responding to the third authorization request by linking the second partner actor to the first partner actor in the trust stack, and sending a third token to the second actor partner with a third set of permissions, where the third token comprises a second complex token that identifies the first partner actor and the second partner actor.

Examples in accordance with certain aspects of the disclosed technology can further include receiving an access request to a resource from the second partner actor, the access request including the third token and granting access to the resource based on the third set of permissions. Other examples in accordance with other aspects of the disclosed technology can include determining the second set of permissions based on either a union or intersection of permissions for the subject client and permissions for the first partner actor. In still other examples, the disclosed technologies can include determining the third set of permissions based on either a union or intersection of permissions for the subject client, permissions for the first partner actor, and permissions for the third partner actor.

In certain examples, the authorization delegation pertains to a financial transaction, the first partner actor is not configured for compliance with a standard for secure handling of customer financial data, and the second partner actor is configured for compliance with the standard for secure handling of customer financial data.

In certain other examples, the subject client can be an end user, the first partner actor can be a service provider to the end user, and the second partner actor can be a subcontractor to the first partner. In certain of these examples, the second partner actor is configured to provide one or more of shipping, packaging, warehousing and insurance to the first partner.

It should be appreciated that the above-described subject matter may also be implemented as a computer-controlled apparatus, a computer process, a computing system, or as an article of manufacture such as a computer-readable medium. These and various other features will be apparent from a reading of the following Detailed Description and a review of the associated drawings.

This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended that this Summary be used to limit the scope of the claimed subject matter.

The following Detailed Description describes technologies for complex delegation of OAuth permissions. While a current OAuth proposal provides for delegation of permission from a subject entity to an actor entity using composite tokens, the disclosed technology provides for creation of a trust stack that stores permissions and relationships between multiple entities that permits traceable delegation between multiple entities using complex composite tokens.

Recently, an Internet Engineering Task Force (IETF) draft for OAuth <NUM> Token Exchange, https://tools. org/html/draft-ietf-oauth-token-exchange-<NUM>, proposed an approach that allows delegation of tokens by combining a pair of tokens into a composite token. Each composite token includes a subject token, e.g. a token for a subject entity that is buying an item or receiving sensitive data, and an actor token, e.g. a token for an actor entity, such as a payment provider or HIPPA compliant service, acting on behalf of the subject entity.

The resulting composite token of the subject and actor tokens can be used by the actor entity to act on behalf of the subject entity. The composite token provides for the subject entity to maintain its own identity separate from the actor entity and explicitly indicates that the actor is acting on behalf of the subject.

In contrast, the disclosed technology allows a chain of trust to be established for multiple delegations of permissions using complex composite tokens. This involves maintaining a trust stack that identifies the entities and tokens in each delegation and the relationships between the entities. In certain aspects of the disclosed technology, the manner in which permissions are delegated in the complex composite tokens can be controlled. The delegations of permissions can be readily audited and the entities identified using the trust stack.

In the disclosed technology, a chain can be formed using composite tokens issued by an OAuth server that maintains the association between the composite tokens and individual tokens. The following is an illustrative example of a chain of trust:
{Token <NUM>} -> {Token <NUM> | Token <NUM>} -> {Token <NUM> | Token <NUM>}.

In this example of a chain of trust, the access allowed to composite token {Token <NUM> | Token <NUM>} can also allow access to data or APIs to {Token <NUM>} because of the chain of trust linking individual token {Token <NUM>} to composite token {Token <NUM> | Token <NUM>} through composite token {Token <NUM> | Token <NUM>}. The OAuth service that manages the sending of complex composite token will maintain a trust stack that represents (<NUM>) the parties acting on behalf of each other within the chain of trust and (<NUM>) the call stack in the chain of trust for the transaction.

The disclosed technology can permit a platform to allow an indefinite number of N actors to participate in a transaction on the platform. In some implementations, the disclosed technology can permit the platform to coordinate sub-transactions among the N actors.

In certain examples, a variety of different solutions can be implemented for controlling the delegation of permissions in the chain of trust. For example, assume Token <NUM> allows API <NUM> to be called and Token <NUM> allows API <NUM> to be called. In some examples, the permissions associated with a composite token can be the intersection of the permissions of the individual tokens in the composite token. Thus, the composite token {Token <NUM> | Token <NUM>} allow only API <NUM> to be called.

In other examples, the permissions associated with a composite token can be the union of the permissions of the individual tokens in the composite token. In these examples, the composite token {Token <NUM> | Token <NUM>} allows both API <NUM> and API <NUM> to be called.

These are simplified examples and many factors may be considered in a system or method for OAuth multiple actor delegation using complex composite tokens.

Because the trust stack allows for granular permissions across different actors, it offers a technical advantage of improved security of computer systems, computer servers, and/or data centers. Further, because the trust stack data structure allows for an efficient mechanism to look up partners interacting on a transaction, so it may improve performance and processing efficiency of a machine. As just one example, an O(log(N)) look up on trust stacks may be used to discover whether a token is already in use in a trust stack (if there is an index of tokens to trust stacks), and therefore look up of partner entities operating on a transaction may be extremely fast. Because look up of the trust stack is fast, and permissions may be directly associated with security tokens, processing performance to determine permissions allowable by different entities operating on a transaction may be further improved.

As will be described in more detail herein, it can be appreciated that implementations of the techniques and technologies described herein may include the use of solid state circuits, digital logic circuits, computer components, and/or software executing on one or more input devices. Signals described herein may include analog and/or digital signals for communicating a changed state of the data file or other information pertaining to the data file.

While the subject matter described herein is presented in the general context of program modules that execute in conjunction with the execution of an operating system and application programs on a computer system, those skilled in the art will recognize that other implementations may be performed in combination with other types of program modules. Generally, program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the subject matter described herein may be practiced with other computer system configurations, including multiprocessor systems, mainframe computers, microprocessor-based or programmable consumer electronics, minicomputers, hand-held devices, and the like.

By the use of the technologies described herein, a trust stack is created that stores permissions and relationships between multiple entities and permits traceable delegation between the multiple entities using complex composite tokens. Other technical effects other than those mentioned herein can also be realized from implementation of the technologies disclosed herein.

In the following detailed description, references are made to the accompanying drawings that form a part hereof, and in which are shown by way of illustration specific configurations or examples. Referring now to the drawings, in which like numerals represent like elements throughout the several figures, aspects of a computing system, computer-readable storage medium, and computer-implemented methodologies for trust delegation will be described. As will be described in more detail below with respect to the figures, there are a number of applications and services that may embody the functionality and techniques described herein.

<FIG> is an architectural diagram showing an illustrative example of an architecture <NUM> suitable for application of the disclosed technology for OAuth multiple actor delegation using complex composite tokens. In the example of <FIG>, a client, such as a consumer's mobile client device, acting as a subject entity can communicate with partner servers 120A-C and OAuth server <NUM> through network <NUM>. Partner servers 120A-C can communicate with one another and OAuth server <NUM> to transfer, for example, authentication data and other data relating to a transaction, such as a data transfer or a purchase transaction. OAuth server <NUM> can be a platform for controlling the transaction as well as managing authentication tokens for client <NUM> and partner server 120A-C.

<FIG> is a data architecture diagram showing an illustrative example of a data exchange <NUM> in an application of the disclosed technology for complex delegation of OAuth permissions. In this example, client <NUM>, as a subject entity, initiates an authentication flow, at <NUM>, to obtain an authentication token from OAuth server <NUM> that permits access to a computer resource, such as one or more APIs. At <NUM>, if authentication is successful, OAuth server <NUM> sends Token1 to client <NUM>. While OAuth is used in at least some embodiments, it is to be appreciated that a trust stack may be used in any security or other networking protocols.

At <NUM>, client <NUM> delegates access to partner server 120A, by sending Token1 so that partner server 120A can be an actor entity for the subject entity of client <NUM>. At <NUM>, partner server 120A registers Token1 with OAuth server <NUM>. In response, OAuth server <NUM> registers Token1, generates Token <NUM> for partner server 120A, and creates composite token Token1:Token2, which is provided to partner server 120A at <NUM>. At this point, the subject entity of client <NUM> has delegated its permissions to the actor entity of partner server 120A in accordance with the IETF OAuth proposal discussed above.

In accordance with the disclosed technology, partner server 120A further delegates access to partner server 120B as another actor entity by sending composite token Token1:Token2 at <NUM>. At <NUM>, partner server 120B registers composite token Token1:Token2 with OAuth server <NUM>. OAuth server <NUM> creates a chain of trust by recording the delegation indicated in composite token Token1:Token2 in a trust stack that indicates the relationship of Token2 to Token1 along with the devices associated with each of Token1 and Token2. OAuth server generates Token3 for partner server 120B, which is recorded in the trust stack along with the device associated with Token3 and indicating the relationship of Token3 to Token2, and creates a complex composite token Token2:Token3, which it sends to partner server 120B at <NUM>.

At <NUM>, partner server 120B further delegates access to partner server 120C as yet another actor entity by sending complex composite token Token2:Token3. Partner server 120C registers complex composite token Token2:Token3 with OAuth server <NUM>. OAuth server <NUM> records the delegation indicated in complex composite token Token2:Token3 in the trust stack. OAuth server <NUM> generates Token4 for partner server 120C, which is recorded in the trust stack along with the device associated with Token4, e.g. partner server 120C, to indicate the relationship of Token4 to Token3, and creates complex composite token Token4:Token3, which it sends to partner server 120C at <NUM>. Optionally, OAuth server <NUM> may maintain one or more indexes of the trust stack so that the trust stack(s) associated with a token is quickly identified, and the position of the token within the trust stack quickly found. It is to be appreciated that a trust stack may include simple tokens, complex tokens, and/or any combination of the types of token.

<FIG> is a data architecture diagram showing an illustrative example of complex delegation of permissions for a payment workflow <NUM>. In this example, at <NUM>, a client buyer <NUM> initiates completion of a transaction through eCommerce platform <NUM>, at <NUM>, with seller partner server 120A and, at <NUM>, tenders payment to seller partner server 120A, which is not PCI compliant. It is to be appreciated that while <FIG> depicts an eCommerce platform, the trust stack may be used in any web environment that requires authentication and/or authorization by various entities, and where it is desirable to store tokens allocated across entities as well as delegation of authority by one or more of those entities. As a second example, such authorization may be for storage of data in a database.

Because seller partner server 120A is not PCI compliant, it will delegate receiving payment to another partner entity that is PCI compliant. At <NUM>, seller partner server 120A registers with eCommerce platform <NUM> to obtain a first access token Token1 for obtaining access to the client buyer's payment information, which is sent at <NUM>.

At <NUM>, seller partner server 120A delegates receipt of payment to partner server 120B, which is indicated in a complex token that identifies seller partner server 120A as the subject entity and partner server 120B as the actor entity and includes Token1. Upon receipt of the delegation, at <NUM>, partner server 120B registers with eCommerce platform <NUM> and, at <NUM>, receives complex token {Token1, Token2}.

In tum, partner server 120B, at <NUM>, delegates payment receipt to partner server 120C, which is a PCI compliant vault that contains the payment information for client buyer <NUM>. At <NUM>, partner server 120C registers with eCommerce platform <NUM> and, at <NUM>, receives complex token {Token2, Token3}, which grants access to partner server 120C to submit the client buyer's payment information via a payment API of eCommerce platform <NUM>.

The payment work flow <NUM> of <FIG> illustrates one example of a payment workflow in which partner server 120C acts to obtain payment on behalf of partner seller server 120A. The delegation of trust in this scenario will be maintained by eCommerce platform <NUM> in a trust stack. As will be readily appreciated by one of ordinary skill in the art, many variations on this payment workflow are possible without departing from the teachings of the disclosed technology.

<FIG> is a data architecture diagram showing an illustrative example of complex delegation of permissions for a shipment workflow <NUM>. In this scenario, seller partner server 120A delegates shipment of an item purchased by buyer client <NUM> to a partner servers 120B and 120C. For example, partner server 120B can obtain and pack the item and then provide it to partner server 120C for bulk shipment.

At <NUM>, client buyer <NUM> sends a request to ship the item to partner seller server 120A. At <NUM>, partner seller server 120A registers with eCommerce platform <NUM> and, at <NUM>, receives access Token1. For example, access Token1 can provide access to the client buyer's home shipping information.

At <NUM>, seller partner server 120A delegates shipment of the item to partner server 120B, e.g. a courier, packer or warehouse, which is indicated in a complex token that identifies seller partner server 120A as the subject entity and partner server 120B as the actor entity and includes Token1. At <NUM>, partner server 120B registers with eCommerce platform <NUM> and, at <NUM>, receives complex token {Token1, Token2}.

In tum, partner server 120B, at <NUM>, delegates bulk shipment to partner server 120C. For example, partner server 120B picks and packs the item for seller partner server 120A and then delegates bulk shipment of the item to partner server 120C. At <NUM>, partner server 120C registers with eCommerce platform <NUM> and, at <NUM>, receives complex token {Token2, Token3}, which, for example, grants access to partner server 120C to obtain the client buyer's payment shipment information via a shipping API of eCommerce platform <NUM> and, at <NUM>, ships the item to the client buyer's shipping address.

The payment work flow <NUM> of <FIG> illustrates one example of a shipping workflow in which partner servers 120B and 120C act on behalf of partner seller server 120A to fulfill shipment of the item purchased by client buyer <NUM>. The delegation of trust in this scenario will be maintained by eCommerce platform <NUM> in a trust stack.

As will be readily appreciated by one of ordinary skill in the art, many variations on this shipping workflow are possible without departing from the teachings of the disclosed technology. For example, another partner server may be involved in insuring shipment of the item on behalf of seller partner server 120A.

In addition, the trust stack and delegation scheme of the disclosed technology can be utilized to implement a wide variety of work flow schemes. For example, the trust stack and delegation scheme can, in some examples, be combined with workflow management functionality to control and direct work flows involving complex permissions and delegations.

The trust stack resulting from the example of <FIG> is shown in <FIG>, which is a data architecture diagram showing an architecture <NUM> for a complex delegation of OAuth permissions created by the delegations illustrated in <FIG>. In this example, each authentication layer <NUM> includes an identifier <NUM> for an authorized entity, an access token <NUM>, a set of defined permissions <NUM> associated with the access token, and a permissions delegation indicator <NUM> indicating how delegated permissions are handled. For each delegation, the delegating layer and delegatee layer are linked or otherwise associated, e.g. in a table or list. For example, for the delegation from client <NUM> to partner server 120A, layer 310A, which contains the identifier for client <NUM> along with access Token1 and permissions associated with Token1, e.g. API1, is linked to layer 310B, which contains the identifier for partner server 120A along with access Token2 and permissions associated with Token2, e.g. API1 and API2.

Similarly, for the delegation from partner server 120A to partner server 120B, layer 310B is linked to layer 310C, which contains the identifier for partner server 120B along with access Token3 and permissions associated with Token3, e.g. API1, API2 and API3. For the delegation from partner server 120B to partner server 120C, layer 310C is linked to layer 310D, which contains the identifier for partner server 120C along with access Token4 and permissions associated with Token3, e.g. API1, API2 and API3.

The trust stack or data structure <NUM> is maintained in OAuth server <NUM>, which adds a layer to the trust stack for each successful delegation. Note that the disclosed technology is not limited to the data structure shown. Also note that, depending upon the implementation and desired features, either more or less data can be incorporated into the trust stack. Also, as noted above, the trust stack and delegation scheme described herein can be combined, in some examples, with complex workflows and workflow management. It will be readily understood that a variety of data forms can be utilized to represent the multiple delegations of permissions in accordance with the disclosed technology.

<FIG> is a data architecture diagram showing an illustrative example of the delegation of permissions <NUM> in the trust stack <NUM> of <FIG> in an application of the disclosed technology for complex delegation of OAuth permissions. As noted above with respect to <FIG>, a permissions delegation indicator <NUM> indicating how delegated permissions are handled, e.g. by OAuth server <NUM>, in determining which permissions have been delegated.

For example, the permissions delegation indicator <NUM> can indicate that only the intersection of permissions <NUM> granted in association with each token <NUM> at each level are able to be delegated. The OAuth server <NUM> determines the intersection of the permissions <NUM> of the layers in trust stack <NUM> to determine the permissions delegated. In the example of <FIG>, the only permissions common to the permissions 316A-D is API1. Thus, the permissions delegated in this scenario are limited to access to API1.

In another example, the permissions delegation indicator <NUM> can indicate that the union of permissions <NUM> granted in association with each token <NUM> at each level are able to be delegated. The OAuth server <NUM> determines the union of the permissions <NUM> of the layers in trust stack <NUM> to determine the permissions delegated to partner server 120D. In the example of <FIG>, all permissions included in the permissions 316A-D are delegated to partner server 120D. Thus, the permissions delegated to partner server 120D in this scenario provide access to API1, API2 and API3.

Notably, while <FIG> depicts association of different permissions to different APIs in association with the tokens in the trust stack, other data may be associated with the tokens in the trust stack. For example, user profiles, or cache data may be associated with the tokens in the trust stack. Any data useful to complete a distributed transaction associated with the entities operating in the trust stack may be maintained.

<FIG> is a control flow diagram showing an illustrative example of a process <NUM> for complex delegation of OAuth permissions in accordance with the disclosed technology. At <NUM>, an authentication request is received from a client. For example, OAuth server <NUM> receives an authentication request from client <NUM> in <FIG>. At <NUM>, OAuth server <NUM> responds with a first access token with, in this example, permission to access API1.

At <NUM>, an authorization is received from a first partner, where the authorization request includes the first token. Because of the presence of the first token in the request, OAuth server <NUM> recognizes the request as a delegation from the client to the first server, e.g. client <NUM> to partner server 120A. At <NUM>, OAuth server <NUM> links the first partner to the client in the trust stack, e.g. creates layer 310A in trust stack <NUM> in <FIG>, and responds to the authorization request from the first partner with a second token, which is a complex token that indicates the client as the subject entity and the first partner as the actor entity.

At <NUM>, an authorization request is received from a second partner, e.g. partner server 120B that includes the second token. The presence of the second token indicates to the OAuth server <NUM> that the first partner has delegated to the second partner. At <NUM>, the second partner is linked to the first partner in the trust stack, e.g. by creation of layer 310B in trust stack <NUM>, and a third token, which is a complex token that indicates the first partner as the subject entity and the second partner as the actor entity, is generated and sent to the second partner.

At <NUM>, an authorization request is received from a third partner that includes the third token. This indicates to the OAuth server <NUM> that the second partner has delegated to the third partner. At <NUM>, the third partner is linked to the second partner in the trust stack, e.g. by creation of layer 310C in trust stack <NUM>, and a fourth token, which is a complex token that indicates the second partner as the subject entity and the third partner as the actor entity, is generated and sent to the third partner.

The steps of process <NUM> can be extended to add additional layers to the trust stack representing further delegations. The OAuth server <NUM> maintains the trust stack, which illustrates each delegation of authority.

It should be appreciated that a variety of different instrumentalities and methodologies can be utilized to establish wireless communication as well as collect, exchange and display sensor and message data without departing from the teachings of the disclosed technology. The disclosed technology provides a high degree of flexibility and variation in the configuration of implementations without departing from the teachings of the present disclosure.

The present techniques may involve operations occurring in one or more machines. As used herein, "machine" means physical data-storage and processing hardware programed with instructions to perform specialized computing operations. It is to be understood that two or more different machines may share hardware components. For example, the same integrated circuit may be part of two or more different machines.

One of ordinary skill in the art will recognize that a wide variety of approaches may be utilized and combined with the present approach to trust delegation. The specific examples of different aspects of trust delegation described herein are illustrative and are not intended to limit the scope of the techniques shown.

Note that at least parts of processes <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> of FIGURES 4A, 4B, 4C, 4D, 4E and 4F and other processes and operations pertaining to trust delegation described herein may be implemented in one or more servers, such as computer environment <NUM> in <FIG>, or the cloud, and data defining the results of user control input signals translated or interpreted as discussed herein may be communicated to a user device for display. Alternatively, the trust delegation processes may be implemented in a client device. In still other examples, some operations may be implemented in one set of computing resources, such as servers, and other steps may be implemented in other computing resources, such as a client device.

It should be understood that the methods described herein can be ended at any time and need not be performed in their entireties. Some or all operations of the methods described herein, and/or substantially equivalent operations, can be performed by execution of computer-readable instructions included on a computer-storage media, as defined below. The term "computer-readable instructions," and variants thereof, as used in the description and claims, is used expansively herein to include routines, applications, application modules, program modules, programs, components, data structures, algorithms, and the like. Computer-readable instructions can be implemented on various system configurations, including single-processor or multiprocessor systems, minicomputers, mainframe computers, personal computers, hand-held computing devices, microprocessor-based, programmable consumer electronics, combinations thereof, and the like.

Thus, it should be appreciated that the logical operations described herein are implemented (<NUM>) as a sequence of computer implemented acts or program modules running on a computing system and/or (<NUM>) as interconnected machine logic circuits or circuit modules within the computing system. The implementation is a matter of choice dependent on the performance and other requirements of the computing system. Accordingly, the logical operations described herein are referred to variously as states, operations, structural devices, acts, or modules. These operations, structural devices, acts, and modules may be implemented in software, in firmware, in special purpose digital logic, and any combination thereof.

As described herein, in conjunction with the FIGURES described herein, the operations of the routines (e.g. processes <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> of FIGURES 4A, 4B, 4C, 4D, 4E and 4F) are described herein as being implemented, at least in part, by an application, component, and/or circuit. Although the following illustration refers to the components of FIGURES 4A-F, it can be appreciated that the operations of the routines may be also implemented in many other ways. For example, the routines may be implemented, at least in part, by a computer processor or a processor or processors of another computer. In addition, one or more of the operations of the routines may alternatively or additionally be implemented, at least in part, by a computer working alone or in conjunction with other software modules.

For example, the operations of routines are described herein as being implemented, at least in part, by an application, component and/or circuit, which are generically referred to herein as modules. In some configurations, the modules can be a dynamically linked library (DLL), a statically linked library, functionality produced by an application programing interface (API), a compiled program, an interpreted program, a script or any other executable set of instructions. Data and/or modules, such as the data and modules disclosed herein, can be stored in a data structure in one or more memory components. Data can be retrieved from the data structure by addressing links or references to the data structure.

Although the following illustration refers to the components of the FIGURES discussed above, it can be appreciated that the operations of the routines (e.g. processes <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> of FIGURES 4A, 4B, 4C, 4D, 4E and 4F) may be also implemented in many other ways. For example, the routines may be implemented, at least in part, by a processor of another remote computer or a local computer or circuit. In addition, one or more of the operations of the routines may alternatively or additionally be implemented, at least in part, by a chipset working alone or in conjunction with other software modules. Any service, circuit or application suitable for providing the techniques disclosed herein can be used in operations described herein.

<FIG> shows additional details of an example computer architecture <NUM> for a computer, such as the devices <NUM> and 120A-C (<FIG> and <FIG>), capable of executing the program components described herein. Thus, the computer architecture <NUM> illustrated in <FIG> illustrates an architecture for an on-board vehicle computer, a server computer, mobile phone, a PDA, a smart phone, a desktop computer, a netbook computer, a tablet computer, an on-board computer, a game console, and/or a laptop computer. The computer architecture <NUM> may be utilized to execute any aspects of the software components presented herein.

The computer architecture <NUM> illustrated in <FIG> includes a central processing unit <NUM> ("CPU"), a system memory <NUM>, including a random access memory <NUM> ("RAM") and a read-only memory ("ROM") <NUM>, and a system bus <NUM> that couples the memory <NUM> to the CPU <NUM>. A basic input/output system containing the basic routines that help to transfer information between subelements within the computer architecture <NUM>, such as during startup, is stored in the ROM <NUM>. The computer architecture <NUM> further includes a mass storage device <NUM> for storing an operating system <NUM>, data (such as permissions information <NUM>, trust stack information <NUM>, and workflow information <NUM>), and one or more application programs.

The mass storage device <NUM> is connected to the CPU <NUM> through a mass storage controller (not shown) connected to the bus <NUM>. The mass storage device <NUM> and its associated computer-readable media provide non-volatile storage for the computer architecture <NUM>. Although the description of computer-readable media contained herein refers to a mass storage device, such as a solid-state drive, a hard disk or CD-ROM drive, it should be appreciated by those skilled in the art that computer-readable media can be any available computer storage media or communication media that can be accessed by the computer architecture <NUM>.

Communication media includes computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any delivery media. The term "modulated data signal" means a signal that has one or more of its characteristics changed or set in a manner so as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of any of the above should also be included within the scope of computer-readable media.

By way of example, and not limitation, computer storage media may include volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data. For example, computer media includes, but is not limited to, RAM, ROM, EPROM, EEPROM, flash memory or other solid state memory technology, CD-ROM, digital versatile disks ("DVD"), HD-DVD, BLU-RAY, or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the computer architecture <NUM>. For purposes the claims, the phrase "computer storage medium," "computer-readable storage medium" and variations thereof, does not include waves, signals, and/or other transitory and/or intangible communication media, per se.

According to various configurations, the computer architecture <NUM> may operate in a networked environment using logical connections to remote computers through the network <NUM> and/or another network (not shown). The computer architecture <NUM> may connect to the network <NUM> through a network interface unit <NUM> connected to the bus <NUM>. It should be appreciated that the network interface unit <NUM> also may be utilized to connect to other types of networks and remote computer systems. The computer architecture <NUM> also may include an input/output controller <NUM> for receiving and processing input from a number of other devices, including a keyboard, mouse, game controller, television remote or electronic stylus (not shown in <FIG>). Similarly, the input/output controller <NUM> may provide output to a display screen, a printer, or other type of output device (also not shown in <FIG>).

It should be appreciated that the software components described herein may, when loaded into the CPU <NUM> and executed, transform the CPU <NUM> and the overall computer architecture <NUM> from a general-purpose computing system into a special-purpose computing system customized to facilitate the functionality presented herein. The CPU <NUM> may be constructed from any number of transistors or other discrete circuit elements, which may individually or collectively assume any number of states. More specifically, the CPU <NUM> may operate as a finite-state machine, in response to executable instructions contained within the software modules disclosed herein. These computer-executable instructions may transform the CPU <NUM> by specifying how the CPU <NUM> transitions between states, thereby transforming the transistors or other discrete hardware elements constituting the CPU <NUM>.

As another example, the computer-readable media disclosed herein may be implemented using magnetic or optical technology. In such implementations, the software presented herein may transform the physical state of magnetic or optical media, when the software is encoded therein. These transformations may include altering the magnetic characteristics of particular locations within given magnetic media. These transformations also may include altering the physical features or characteristics of particular locations within given optical media, to change the optical characteristics of those locations. Other transformations of physical media are possible without departing from the scope and spirit of the present description, with the foregoing examples provided only to facilitate this discussion.

In light of the above, it should be appreciated that many types of physical transformations take place in the computer architecture <NUM> in order to store and execute the software components presented herein. It also should be appreciated that the computer architecture <NUM> may include other types of computing devices, including hand-held computers, embedded computer systems, personal digital assistants, and other types of computing devices known to those skilled in the art. It is also contemplated that the computer architecture <NUM> may not include all of the components shown in <FIG>, may include other components that are not explicitly shown in <FIG>, or may utilize an architecture completely different than that shown in <FIG>.

<FIG> depicts an illustrative distributed computing environment <NUM> capable of executing the software components described herein for trust delegation. Thus, the distributed computing environment <NUM> illustrated in <FIG> can be utilized to execute many aspects of the software components presented herein. For example, the distributed computing environment <NUM> can be utilized to execute one or more aspects of the software components described herein.

According to various implementations, the distributed computing environment <NUM> includes a computing environment <NUM> operating on, in communication with, or as part of the network <NUM>. The network <NUM> may be or may include the network <NUM>, described above. The network <NUM> also can include various access networks. One or more client devices 606A-806N (hereinafter referred to collectively and/or generically as "clients <NUM>") can communicate with the computing environment <NUM> via the network <NUM> and/or other connections (not illustrated in <FIG>). In one illustrated configuration, the clients <NUM> include a computing device 606A, such as a laptop computer, a desktop computer, or other computing device; a slate or tablet computing device ("tablet computing device") 606B; a mobile computing device 606C such as a mobile telephone, a smart phone, an on-board computer, or other mobile computing device; a server computer 606D; and/or other devices 606N, which can include a hardware security module. It should be understood that any number of devices <NUM> can communicate with the computing environment <NUM>. Two example computing architectures for the devices <NUM> are illustrated and described herein with reference to <FIG> and <FIG>. It should be understood that the illustrated devices <NUM> and computing architectures illustrated and described herein are illustrative only and should not be construed as being limited in any way.

In the illustrated configuration, the computing environment <NUM> includes application servers <NUM>, data storage <NUM>, and one or more network interfaces <NUM>. According to various implementations, the functionality of the application servers <NUM> can be provided by one or more server computers that are executing as part of, or in communication with, the network <NUM>. The application servers <NUM> can host various services, virtual machines, portals, and/or other resources. In the illustrated configuration, the application servers <NUM> host one or more virtual machines <NUM> for hosting applications or other functionality. According to various implementations, the virtual machines <NUM> host one or more applications and/or software modules for trust delegation. It should be understood that this configuration is illustrative only and should not be construed as being limiting in any way.

According to various implementations, the application servers <NUM> also include one or more authentication services <NUM>, trust stack services <NUM>, permission services <NUM> and workflow management services <NUM>. The authentication services <NUM> can include services for handling authentication requests and issuing tokens. The trust stack services <NUM> can include services for maintaining a trust stack indicating the trust delegation relationships between entities. The permission services <NUM> can include services for managing permissions granted with respect to tokens. The workflow management services <NUM> can includes services for defining and managing the structure of complex work flows.

As shown in <FIG>, the application servers <NUM> also can host other services, applications, portals, and/or other resources ("other resources") <NUM>. The other resources <NUM> can include, but are not limited to, data encryption, data sharing, or any other functionality.

As mentioned above, the computing environment <NUM> can include data storage <NUM>. According to various implementations, the functionality of the data storage <NUM> is provided by one or more databases or data stores operating on, or in communication with, the network <NUM>. The functionality of the data storage <NUM> also can be provided by one or more server computers configured to host data for the computing environment <NUM>. The data storage <NUM> can include, host, or provide one or more real or virtual data stores 626A-826N (hereinafter referred to collectively and/or generically as "datastores <NUM>"). The datastores <NUM> are configured to host data used or created by the application servers <NUM> and/or other data. Aspects of the datastores <NUM> may be associated with services for a trust delegation. Although not illustrated in <FIG>, the datastores <NUM> also can host or store web page documents, word documents, presentation documents, data structures, algorithms for execution by a recommendation engine, and/or other data utilized by any application program or another module.

The computing environment <NUM> can communicate with, or be accessed by, the network interfaces <NUM>. The network interfaces <NUM> can include various types of network hardware and software for supporting communications between two or more computing devices including, but not limited to, mobile client vehicles, the clients <NUM> and the application servers <NUM>. It should be appreciated that the network interfaces <NUM> also may be utilized to connect to other types of networks and/or computer systems.

It should be understood that the distributed computing environment <NUM> described herein can provide any aspects of the software elements described herein with any number of virtual computing resources and/or other distributed computing functionality that can be configured to execute any aspects of the software components disclosed herein. According to various implementations of the concepts and technologies disclosed herein, the distributed computing environment <NUM> may provide the software functionality described herein as a service to the clients using devices <NUM>. It should be understood that the devices <NUM> can include real or virtual machines including, but not limited to, server computers, web servers, personal computers, mobile computing devices, smart phones, and/or other devices, which can include user input devices. As such, various configurations of the concepts and technologies disclosed herein enable any device configured to access the distributed computing environment <NUM> to utilize the functionality described herein for trust delegation, among other aspects.

Turning now to <FIG>, an illustrative computing device architecture <NUM> for a computing device that is capable of executing various software components is described herein for trust delegation. The computing device architecture <NUM> is applicable to computing devices such as mobile clients in vehicles. In some configurations, the computing devices include, but are not limited to, mobile telephones, on-board computers, tablet devices, slate devices, portable video game devices, traditional desktop computers, portable computers (e.g., laptops, notebooks, ultra-portables, and netbooks), server computers, game consoles, and other computer systems. The computing device architecture <NUM> is applicable to the client device <NUM> and client/servers 120A-C shown in <FIG>, <FIG>, and computing device 606A-N shown in <FIG>.

The computing device architecture <NUM> illustrated in <FIG> includes a processor <NUM>, memory components <NUM>, network connectivity components <NUM>, sensor components <NUM>, input/output components <NUM>, and power components <NUM>. In the illustrated configuration, the processor <NUM> is in communication with the memory components <NUM>, the network connectivity components <NUM>, the sensor components <NUM>, the input/output ("I/O") components <NUM>, and the power components <NUM>. Although no connections are shown between the individual components illustrated in <FIG>, the components can interact to carry out device functions. In some configurations, the components are arranged so as to communicate via one or more busses (not shown).

The processor <NUM> includes a central processing unit ("CPU") configured to process data, execute computer-executable instructions of one or more application programs, and communicate with other components of the computing device architecture <NUM> in order to perform various functionality described herein. The processor <NUM> may be utilized to execute aspects of the software components presented herein and, particularly, those that utilize, at least in part, secure data.

In some configurations, the processor <NUM> includes a graphics processing unit ("GPU") configured to accelerate operations performed by the CPU, including, but not limited to, operations performed by executing secure computing applications, general-purpose scientific and/or engineering computing applications, as well as graphics-intensive computing applications such as high resolution video (e.g., 620P, 1080P, and higher resolution), video games, three-dimensional ("3D") modeling applications, and the like. In some configurations, the processor <NUM> is configured to communicate with a discrete GPU (not shown). In any case, the CPU and GPU may be configured in accordance with a co-processing CPU/GPU computing model, wherein a sequential part of an application executes on the CPU and a computationally-intensive part is accelerated by the GPU.

In some configurations, the processor <NUM> is, or is included in, a system-on-chip ("SoC") along with one or more of the other components described herein below. For example, the SoC may include the processor <NUM>, a GPU, one or more of the network connectivity components <NUM>, and one or more of the sensor components <NUM>. In some configurations, the processor <NUM> is fabricated, in part, utilizing a package-on-package ("PoP") integrated circuit packaging technique.

The processor <NUM> may be created in accordance with an ARM architecture, available for license from ARM HOLDINGS of Cambridge, United Kingdom. Alternatively, the processor <NUM> may be created in accordance with an x86 architecture, such as is available from INTEL CORPORATION of Mountain View, California and others. In some configurations, the processor <NUM> is a SNAPDRAGON SoC, available from QUALCOMM of San Diego, California, a TEGRA SoC, available from NVIDIA of Santa Clara, California, a HUMMINGBIRD SoC, available from SAMSUNG of Seoul, South Korea, an Open Multimedia Application Platform ("OMAP") SoC, available from TEXAS INSTRUMENTS of Dallas, Texas, a customized version of any of the above SoCs, or a proprietary SoC.

The memory components <NUM> include a random access memory ("RAM") <NUM>, a read-only memory ("ROM") <NUM>, an integrated storage memory ("integrated storage") <NUM>, and a removable storage memory ("removable storage") <NUM>. In some configurations, the RAM <NUM> or a portion thereof, the ROM <NUM> or a portion thereof, and/or some combination of the RAM <NUM> and the ROM <NUM> is integrated in the processor <NUM>. In some configurations, the ROM <NUM> is configured to store a firmware, an operating system or a portion thereof (e.g., operating system kernel), and/or a bootloader to load an operating system kemel from the integrated storage <NUM> and/or the removable storage <NUM>.

The integrated storage <NUM> can include a solid-state memory, a hard disk, or a combination of solid-state memory and a hard disk. The integrated storage <NUM> may be soldered or otherwise connected to a logic board upon which the processor <NUM> and other components described herein also may be connected. As such, the integrated storage <NUM> is integrated in the computing device. The integrated storage <NUM> is configured to store an operating system or portions thereof, application programs, data, and other software components described herein.

The removable storage <NUM> can include a solid-state memory, a hard disk, or a combination of solid-state memory and a hard disk. In some configurations, the removable storage <NUM> is provided in lieu of the integrated storage <NUM>. In other configurations, the removable storage <NUM> is provided as additional optional storage. In some configurations, the removable storage <NUM> is logically combined with the integrated storage <NUM> such that the total available storage is made available as a total combined storage capacity. In some configurations, the total combined capacity of the integrated storage <NUM> and the removable storage <NUM> is shown to a user instead of separate storage capacities for the integrated storage <NUM> and the removable storage <NUM>.

The removable storage <NUM> is configured to be inserted into a removable storage memory slot (not shown) or other mechanism by which the removable storage <NUM> is inserted and secured to facilitate a connection over which the removable storage <NUM> can communicate with other components of the computing device, such as the processor <NUM>. The removable storage <NUM> may be embodied in various memory card formats including, but not limited to, PC card, CompactFlash card, memory stick, secure digital ("SD"), miniSD, microSD, universal integrated circuit card ("UICC") (e.g., a subscriber identity module ("SIM") or universal SIM ("USIM")), a proprietary format, or the like.

It can be understood that one or more of the memory components <NUM> can store an operating system. According to various configurations, the operating system may include, but is not limited to, server operating systems such as various forms of UNIX certified by The Open Group and LINUX certified by the Free Software Foundation, or aspects of Software-as-a-Service (SaaS) architectures, such as MICROSFT AZURE from Microsoft Corporation of Redmond, Washington or AWS from Amazon Corporation of Seattle, Washington. The operating system may also include WINDOWS MOBILE OS from Microsoft Corporation of Redmond, Washington, WINDOWS PHONE OS from Microsoft Corporation, WINDOWS from Microsoft Corporation, MAC OS or IOS from Apple Inc. of Cupertino, California, and ANDROID OS from Google Inc. of Mountain View, California. Other operating systems are contemplated.

The network connectivity components <NUM> include a wireless wide area network component ("WWAN component") <NUM>, a wireless local area network component ("WLAN component") <NUM>, and a wireless personal area network component ("WPAN component") <NUM>. The network connectivity components <NUM> facilitate communications to and from the network <NUM> or another network, which may be a WWAN, a WLAN, or a WPAN. Although only the network <NUM> is illustrated, the network connectivity components <NUM> may facilitate simultaneous communication with multiple networks, including the network <NUM> of <FIG>. For example, the network connectivity components <NUM> may facilitate simultaneous communications with multiple networks via one or more of a WWAN, a WLAN, or a WPAN.

The network <NUM> may be or may include a WWAN, such as a mobile telecommunications network utilizing one or more mobile telecommunications technologies to provide voice and/or data services to a computing device utilizing the computing device architecture <NUM> via the WWAN component <NUM>. The mobile telecommunications technologies can include, but are not limited to, Global System for Mobile communications ("GSM"), Code Division Multiple Access ("CDMA") ONE, CDMA7000, Universal Mobile Telecommunications System ("UMTS"), Long Term Evolution ("LTE"), and Worldwide Interoperability for Microwave Access ("WiMAX"). Moreover, the network <NUM> may utilize various channel access methods (which may or may not be used by the aforementioned standards) including, but not limited to, Time Division Multiple Access ("TDMA"), Frequency Division Multiple Access ("FDMA"), CDMA, wideband CDMA ("W-CDMA"), Orthogonal Frequency Division Multiplexing ("OFDM"), Space Division Multiple Access ("SDMA"), and the like. Data communications may be provided using General Packet Radio Service ("GPRS"), Enhanced Data rates for Global Evolution ("EDGE"), the High-Speed Packet Access ("HSPA") protocol family including High-Speed Downlink Packet Access ("HSDPA"), Enhanced Uplink ("EUL") or otherwise termed High-Speed Uplink Packet Access ("HSUPA"), Evolved HSPA ("HSPA+"), LTE, and various other current and future wireless data access standards. The network <NUM> may be configured to provide voice and/or data communications with any combination of the above technologies. The network <NUM> may be configured to or be adapted to provide voice and/or data communications in accordance with future generation technologies.

In some configurations, the WWAN component <NUM> is configured to provide dual- multi-mode connectivity to the network <NUM>. For example, the WWAN component <NUM> may be configured to provide connectivity to the network <NUM>, wherein the network <NUM> provides service via GSM and UMTS technologies, or via some other combination of technologies. Alternatively, multiple WWAN components <NUM> may be utilized to perform such functionality, and/or provide additional functionality to support other non-compatible technologies (i.e., incapable of being supported by a single WWAN component). The WWAN component <NUM> may facilitate similar connectivity to multiple networks (e.g., a UMTS network and an LTE network).

The network <NUM> may be a WLAN operating in accordance with one or more Institute of Electrical and Electronic Engineers ("IEEE") <NUM> standards, such as IEEE <NUM>. 11a, <NUM>. 11b, <NUM>, <NUM>. 11n, and/or future <NUM> standard (referred to herein collectively as WI-FI). Draft <NUM> standards are also contemplated. In some configurations, the WLAN is implemented utilizing one or more wireless WI-FI access points. In some configurations, one or more of the wireless WI-FI access points are another computing device with connectivity to a WWAN that are functioning as a WI-FI hotspot. The WLAN component <NUM> is configured to connect to the network <NUM> via the WI-FI access points. Such connections may be secured via various encryption technologies including, but not limited to, WI-FI Protected Access ("WPA"), WPA2, Wired Equivalent Privacy ("WEP"), and the like.

The network <NUM> may be a WPAN operating in accordance with Infrared Data Association ("IrDA"), BLUETOOTH, wireless Universal Serial Bus ("USB"), Z-Wave, ZIGBEE, or some other short-range wireless technology. In some configurations, the WPAN component <NUM> is configured to facilitate communications with other devices, such as peripherals, computers, or other computing devices via the WPAN.

The sensor components <NUM> include a magnetometer <NUM>, an ambient light sensor <NUM>, a proximity sensor <NUM>, an accelerometer <NUM>, a gyroscope <NUM>, and a Global Positioning System sensor ("GPS sensor") <NUM>. It is contemplated that other sensors, such as, but not limited to, temperature sensors or shock detection sensors, also may be incorporated in the computing device architecture <NUM>.

The I/O components <NUM> include a display <NUM>, a touchscreen <NUM>, a data I/O interface component ("data I/O") <NUM>, an audio I/O interface component ("audio I/O") <NUM>, a video I/O interface component ("video I/O") <NUM>, and a camera <NUM>. In some configurations, the display <NUM> and the touchscreen <NUM> are combined. In some configurations two or more of the data I/O component <NUM>, the audio I/O component <NUM>, and the video I/O component <NUM> are combined. The I/O components <NUM> may include discrete processors configured to support the various interfaces described below or may include processing functionality built-in to the processor <NUM>.

The illustrated power components <NUM> include one or more batteries <NUM>, which can be connected to a battery gauge <NUM>. The batteries <NUM> may be rechargeable or disposable. Rechargeable battery types include, but are not limited to, lithium polymer, lithium ion, nickel cadmium, and nickel metal hydride. Each of the batteries <NUM> may be made of one or more cells.

The power components <NUM> may also include a power connector, which may be combined with one or more of the aforementioned I/O components <NUM>. The power components <NUM> may interface with an external power system or charging equipment via an I/O component.

Claim 1:
A computer-implemented authorization delegation method (<NUM>) for extension of OAuth multiple actor delegation, the method being performed by one or more OAuth servers (<NUM>) and comprising:
receiving (<NUM>) a first authorization request from a subject client (<NUM>);
responding (<NUM>) to the first authorization request by sending a first token having a first set of permissions to the subject client (<NUM>);
receiving (<NUM>) a second authorization request from a first partner actor (120A), the second authorization request including the first token;
responding (<NUM>) to the second authorization request by:
linking the first partner actor (120A) to the subject client (<NUM>) in a trust stack (<NUM>) pertaining to the subject client (<NUM>), and
sending a second token to the first partner actor (120A) with a second set of permissions, where the second token comprises a first complex token that identifies the subject client (<NUM>) and the first partner actor (120A);
receiving (<NUM>) a third authorization request from a second partner actor (120B), the third authorization request including the second token;
responding (<NUM>) to the third authorization request by:
linking the second partner actor (120B) to the first partner actor (120A) in the trust stack (<NUM>), and
sending a third token to the second partner actor (120B) with a third set of permissions, where the third token comprises a second complex token that identifies the first partner actor (120A) and the second partner actor (120B).