Page Comparison

...

First download the bash-library source code. For example, if If you have git installed, you can clone the repository as follows:

...

Next download the saml-library source code by cloning the repository:

$ git clone https://github.com/trscavo/saml-library.git

...

The rest of this article assumes you have configured a FileBackedHTTPMetadataProvider in the Shibboleth IdP. The backing file will be used as a source of (trusted) metadata:

$ idp_home=/path/to/idp/home/
$ backing_file="${idp_home%%/}/metadata/federation-metadata.xml"

...

Federations publish metadata files having with Validity Intervals of various lengths. For the sake of illustration, let’s assume the actual Validity Interval in metadata is two weeks (which is actually in fact quite common):

$ maxValidityInterval=P14D

As described in the story referenced at the beginning of this article, to conceptualize the metadata early warning system, we divide the Validity Interval into three subintervals: the Freshness Interval (bounded on the left by the @creationInstant attribute), the Expiration Warning Interval (bounded on the right by the @validUntil attribute), and a no-name subinterval sandwiched in the middle. That isIn effect, the @creationInstant and @validUntil attributes essentially partition the Validity Interval into GREEN, YELLOW, and RED subintervals, respectively.

...

The partition is determined by the lengths of the Freshness Interval and the Expiration Warning Interval. The choice of subinterval lengths depends on the production signing frequency of federation metadata. If we assume the federation publishes fresh metadata at least once every business day, the following subinterval lengths make sense (but YMMV):

...

Yes the Shibboleth IdP ensures that the metadata is valid, and it will even warn you (optionally) if the metadata is soon-to-be-expired, but the IdP is not aware of the @creationInstant attribute and therefore it has no notion of a Freshness Interval. OTOH, the early warning system implemented above does all of the following:

...

1. Assuming the Validity Interval is in fact 14 days, set maxValidityInterval to something less and watch the process fail: an error message will be logged.

2. Again assuming the actual Validity Interval is 14 days, set maxValidityInterval to something more and watch the process fail: a warning message will be logged.

3. Set the freshnessInterval to some ridiculously small value (like PT60S) and watch the process fail: a warning message will be logged.

4. Set the expirationWarningInterval to some ridiculously large value (relative to the actual Validity Interval) and watch the process fail: a warning message will be logged.

Once you've confirmed that the early warning system is behaving as expected, continue with the following configuration steps.

Persisting the Timestamps

Now let’s modify the above command slightly so that the values of the @creationInstant and @validUntil attributes are persisted to a log file. For startersillustration, we’ll configure a log file in the /tmp directory:

...