IP Library › Granted Patent US 11,972,241
Granted Patent B2
US 11,972,241 · App. 17/186,990 · Granted Apr 30, 2024

Validation of payload for deployment to a target environment

Inventors: Dmitry Dmitrievich Garaev (Redmond, WA); Andrey Anatolyevich Lukyanov (Redmond, WA); Nicolae Voicu (Bellevue, WA)
Assignee: Microsoft Technology Licensing, LLC.
G06F8/60H04L9/3236H04L9/3247H04L9/3265H04L9/50
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,972,241
App. No.
17/186,990
Granted
Apr 30, 2024
Kind
B2
Abstract

A payload is generated by a build computing system. The payload includes payload identifying metadata and deployment target identifier metadata, as well as an application container that includes a set of signed binaries. The payload can be approved for deployment, and a token can be generated for the payload. The token may include a set of claims that include payload identifying information. A payload validation system validates the payload for deployment to a target environment using the payload identifying information.

Claims (52)

1. A method performed by a computing system, the method comprising:

receiving a payload including;

a first payload portion having application code configured to be deployed to a target resource cluster,

a second payload portion having payload identifying metadata uniquely identifying the application code in the first payload portion, and

a deployment target identifier that identifies the target resource cluster;

generating a token corresponding to the payload based on the payload identifying metadata, the token including:

a payload identifying claim having a unique identifier that uniquely identifies the application code, and

a deployment target identifier claim based on the deployment target identifier;

controlling a signing system to obtain a signed token by using a signature to electronically sign the token including the payload identifying claim and the deployment target identifier claim; and

outputting a deployment request, including the signed token and the payload, requesting deployment of the payload to the target resource cluster.

2. The method of claim 1 , and further comprising:

identifying an approver system for approving deployment of the payload to the target resource cluster based on the deployment target identifier; and

generating an approval request to the approver system.

3. The method of claim 1 , comprising:

receiving, at a deployment system, the deployment request including the signed token and the payload;

determining whether the payload identifying claim identifies the application code included in the payload;

generating a token/payload correspondence output indicating whether the payload identifying claim identifies the application code included in the payload;

generating a payload validation output indicating whether the payload is validated based at least in part on the token/payload correspondence output; and

controlling the deployment system to deploy the payload to the target resource cluster based on the payload validation output.

4. The method of claim 3 wherein the payload identifying claim comprises a hash value and wherein determining whether the payload identifying claim identifies the application code included in the payload comprises:

hashing the application code in the payload to obtain a code hash value; and

comparing the code hash value to the hash value.

5. The method of claim 3 wherein receiving the deployment request comprises:

receiving the deployment request requesting deployment of the payload to a requested target resource cluster identified by a requested target resource identifier.

6. The method of claim 5 wherein the token includes a deployment target identifier claim identifying a resource cluster and further comprising:

comparing the requested target resource identifier to the deployment target identifier claim.

7. The method of claim 6 wherein generating the payload validation output comprises:

generating the payload validation output based at least in part on whether the requested target resource identifier matches the deployment target identifier claim.

8. The method of claim 7 wherein the token is signed with a signature and further comprising:

validating the signature on the token; and

generating a signature validation output based on validation of the signature.

9. The method of claim 8 wherein controlling the deployment system comprises:

controlling the deployment system to deploy the payload to the target resource cluster based on the payload validation output and the signature validation output.

10. A computing system, comprising:

a processor; and

a data store that has computer executable instructions which cause the processor to implement computing system components, comprising:

a token generator configured to:

receive a payload that includes:

a first payload portion having application code to be deployed to a target resource cluster,

a second payload portion having payload identifying metadata uniquely identifying the application code and

a deployment target identifier that identifies the target resource cluster; and

generate a token corresponding to the payload based on the payload identifying metadata, the token including:

a payload identifying claim having a unique identifier that uniquely identities the application code, and

a deployment target identifier claim based on the deployment target identifier;

a signing system configured to obtain a signed token by using a signature to electronically sign the token including the payload identifying claim and the deployment target identifier claim; and

an output generator configured to generate a deployment request including the signed token and the payload, requesting deployment of the payload to the target resource cluster.

11. The computing system of claim 10 and further comprising:

an approval request generator identifying an approver system for approving deployment of the payload to the target resource cluster based on the deployment target identifier and generating an approval request to the approver system.

12. The computing system of claim 10 and further comprising:

a claim, processing system configured to determine whether the payload identifying claim identifies the application code included in the payload and to generate a token/payload correspondence output indicating whether the payload identifying claim identifies the application code included in the payload and to further generate a payload validation output indicating whether the payload is validated based at least in part on the token/payload correspondence output.

13. The computing system of claim 12 and further comprising:

a target environment validation component configured compare a requested target resource identifier to the deployment target identifier claim and to generate the payload validation output based at least in part on whether the requested target resource identifier matches the deployment target identifier claim.

Assignments (3)
CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNEE'S STATE SHOULD BE "WASHINGTON" PREVIOUSLY RECORDED AT REEL: 058518 FRAME: 0555. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded May 4, 2023
From: GARAEV, DMITRY DMITRIEVICH; LUKYANOV, ANDREY ANATOLYEVICH; VOICU, NICOLAE
To: MICROSOFT TECHNOLOGY LICENSING, LLC
Reel/Frame 063665/0529 →
CORRECTIVE ASSIGNMENT TO CORRECT THE THE SPELLING OF THE FIRST NAME OF THE 3RD INVENTOR PREVIOUSLY RECORDED AT REEL: 056150 FRAME: 0939. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Dec 15, 2021
From: GARAEV, DMITRY DMITRIEVICH; LUKYANOV, ANDREY ANATOLYEVICH; VOICU, NICOLAE
To: MICROSOFT TECHNOLOGY LICENSING, LLC
Reel/Frame 058518/0555 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 5, 2021
From: GARAEV, DMITRY DMITRIEVICH; LUKYANOV, ANDREY ANATOLYEVICH; VOICU, NICOAE
To: MICROSOFT TECHNOLOGY LICENSING, LLC
Reel/Frame 056150/0939 →
Continuity (1)
Related Publication 20220276848A1 · Sep 1, 2022
Cited By (1)
US 12,265,808