Skip to content

Commit 7fd1719

Browse files
nsklikasc00kiemon5ter
authored andcommitted
Update documentation with mdq freshness_period
1 parent 08a071d commit 7fd1719

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

docs/howto/config.rst

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -209,6 +209,7 @@ For example::
209209
{
210210
"url": "http://mdq.ukfederation.org.uk/",
211211
"cert": "ukfederation-mdq.pem",
212+
"freshness_period": "P0Y0M0DT2H0M0S",
212213
},
213214
],
214215
},
@@ -221,6 +222,14 @@ metadata signing certificates should be used. These public keys must be
221222
acquired by some secure out-of-band method before being placed on the local
222223
file system.
223224

225+
When using MDQ, the `freshness_period` option can be set to define
226+
a period for which the metadata fetched from the the MDQ server are considered
227+
fresh. After that period has passed the metadata are not valid anymore and must
228+
be fetched again. The period must be in the format defined in `iso 8601 <https://www.iso.org/iso-8601-date-and-time-format.html>`_.
229+
230+
By default, if `freshness_period` is not defined, the metadata are fetched
231+
only the first time they are requested and never refreshed.
232+
224233
organization
225234
^^^^^^^^^^^^
226235

0 commit comments

Comments
 (0)