Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix #660: Fix documentation for iat and iat_ms in temporary keys #661

Merged
merged 1 commit into from
Oct 7, 2024
+2 −2
Merged

Fix #660: Fix documentation for iat and iat_ms in temporary keys #661

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/Temporary-Encryption-Keys.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ The server then takes the request, generates a random temporary encryption key p
- `applicationKey` - back reference to the original data
- `challenge` - back reference to the original data
- `publicKey` - temporary encryption public key
- `iss` / `iss_ms` - temporary key pair issuance timestamp
- `iat` / `iat_ms` - temporary key pair issuance timestamp
- `exp` / `exp_ms` - temporary key pair expiration timestamp

The client app should process the response by verifying the signature and checking that the application key and challenge match the expected value. Then, the client app can accept the public key with given key identifier.
Expand All @@ -52,7 +52,7 @@ The server then takes the request, generates a random temporary encryption key p
- `activationId` - back reference to the original data
- `challenge` - back reference to the original data
- `publicKey` - temporary encryption public key
- `iss` / `iss_ms` - temporary key pair issuance timestamp
- `iat` / `iat_ms` - temporary key pair issuance timestamp
- `exp` / `exp_ms` - temporary key pair expiration timestamp

The client app should process the response by verifying the signature and checking that the application key, activation ID and challenge match the expected value. Then, the client app can accept the public key with given key identifier.
Expand Down