Complex composite tokens

A system for trust delegation, the system comprising:

• one or more processors;
• and one or more memory devices in communication with the one or more processors, the memory devices having computer-readable instructions stored thereupon that, when executed by the processors, cause the processors to:
• receive a first authorization request from a subject client;
• respond to the first authorization by sending a first token having a first set of permissions to the subject client;
• receive a second authorization request from a first partner actor, the second authorization request including the first token;
• respond 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;
• receive a third authorization request from a second partner actor, the third authorization request including the second token;
• respond 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 and where:
• the subject client comprises an end user;
• the first partner actor comprises a service provider to the end user;
• and the second partner actor comprises a subcontractor to the first partner.

A computer storage medium having computer executable instructions stored thereon which, when executed by one or more processors, cause the processors to execute an authorization delegation method for extension of OAuth multiple actor delegation, the method comprising:

• receiving a first authorization request from a subject client;
• responding to the first authorization by sending a first token having a first set of permissions to the subject client;
• receiving a second authorization request from a first partner actor, the second authorization request including the first token;
• 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;
• receiving a third authorization request from a second partner actor, the third authorization request including the second token;
• 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 and where:
• the subject client comprises an end user;
• the first partner actor comprises a service provider to the end user;
• and the second partner actor comprises a subcontractor to the first partner.