Skip to content

Comments

Comply with JWT#3

Closed
shizhMSFT wants to merge 2 commits intonotaryproject:masterfrom
shizhMSFT:jwt
Closed

Comply with JWT#3
shizhMSFT wants to merge 2 commits intonotaryproject:masterfrom
shizhMSFT:jwt

Conversation

@shizhMSFT
Copy link
Contributor

@shizhMSFT shizhMSFT commented Aug 12, 2020

In this PR, the signature is a JWT variant. Therefore, the signature file is no longer a JSON file.

Additionally, media type is required for the manifest and is verified.

Related: shizhMSFT#16

This is a joint commit of
- Shiwei Zhang
- Steve Lasker
- Aviral Takkar

Signed-off-by: Shiwei Zhang <shizh@microsoft.com>
Signed-off-by: Shiwei Zhang <shizh@microsoft.com>
@trishankatdatadog
Copy link

@shizhMSFT Sorry, I don't understand: how is JWT not JSON? Also, the PR seems to ignore canonicalization altogether for now.

Cc @SantiagoTorress @JustinCappos @mnm678

@shizhMSFT
Copy link
Contributor Author

shizhMSFT commented Aug 20, 2020

@shizhMSFT Sorry, I don't understand: how is JWT not JSON? Also, the PR seems to ignore canonicalization altogether for now.

Cc @SantiagoTorress @JustinCappos @mnm678

A JWT is a concatenation of base64 URL encoded JSON objects. The statement JWT is not JSON is elaborated as A JWT object is not a JSON object but a string of encoded JSON objects.

JSON cannoicalization is not considerred in this PR, and will be included in the next iteration.

/cc @SteveLasker

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants