Reloading local SP data sealer keys

[Wessel, Keith]

Ah-ha! Makes sense. Load and expire it, then don't load it again until it's again needed. Perhaps another debug level message would be in order to clarify why it's loading and purging immediately? Might be excessive, but also might clarify things.

At any rate, thanks for clarifying this as well as how the reload happens in the running SP.

Keith

-----Original Message-----
From: users <users-bounces at shibboleth.net> On Behalf Of Cantor, Scott
Sent: Monday, October 8, 2018 6:21 PM
To: Shib Users <users at shibboleth.net>
Subject: Re: Reloading local SP data sealer keys

On 10/8/18, 1:03 PM, "Cantor, Scott" <cantor.2 at osu.edu> wrote:

> I really have no memory of all the scenarios and interactions. If it's immediate I guess it's for a reason, possibly to expire > the record or something.

The "immediate" log entry is the session cache testing the component at startup to make sure the wrap operation works (essentially it makes sure the key's loaded and working). It's just a test operation.

-- Scott


-- 
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net