Compare commits

...

3 commits

Author SHA1 Message Date
famfo d0eafd6325
Merge 16b98e9097 into 2cc7e13c09 2026-01-12 13:54:26 +00:00
famfo 16b98e9097
changelogs/s2s: add minimum_valid_until_ts clarification 2026-01-06 23:18:32 +01:00
famfo 7f35431eb7
s2s/keys: clarify minimum_valid_until_ts query
Signed-off-by: famfo <famfo@famfo.xyz>
2026-01-06 23:18:32 +01:00
2 changed files with 8 additions and 8 deletions

View file

@ -0,0 +1 @@
Clarify what the `minimum_valid_until_ts` field means when it is set in key queries.

View file

@ -34,10 +34,10 @@ paths:
- in: query
name: minimum_valid_until_ts
description: |-
A millisecond POSIX timestamp in milliseconds indicating when the returned
certificates will need to be valid until to be useful to the requesting server.
A millisecond POSIX timestamp. The returned keys SHOULD be valid
until at least this timestamp.
If not supplied, the current time as determined by the notary server is used.
If not supplied, the notary server SHOULD use the current time.
required: false
example: 1234567890
schema:
@ -98,12 +98,11 @@ paths:
type: integer
format: int64
description: |-
A millisecond POSIX timestamp in milliseconds indicating when
the returned certificates will need to be valid until to be
useful to the requesting server.
A millisecond POSIX timestamp. The returned keys
SHOULD be valid until at least this timestamp.
If not supplied, the current time as determined by the notary
server is used.
If not supplied, the notary server SHOULD use the
current time.
example: 1234567890
required:
- server_keys