From 8bd81bfc38181be8a04bc3c343b7e34de6cfc7cb Mon Sep 17 00:00:00 2001 From: Roman Strobl Date: Mon, 7 Oct 2024 18:55:58 +0800 Subject: [PATCH] Fix #660: Fix documentation for iat and iat_ms in temporary keys --- docs/Temporary-Encryption-Keys.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/Temporary-Encryption-Keys.md b/docs/Temporary-Encryption-Keys.md index 216f80b2..c8136993 100644 --- a/docs/Temporary-Encryption-Keys.md +++ b/docs/Temporary-Encryption-Keys.md @@ -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. @@ -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.