Per-Entity Metadata Working Group

[Thomas Lenggenhager <>]

On 11.08.16 21:55, Cantor, Scott wrote:
> > Scott C, do you envision for "caching"
> >
> > a) writing to disk the metadata for an entity each time it has
> > been fetched successfully to be used to accomplish a SAML flow
>
> Yes. Currently we cache only in RAM. It may be possible to tweak the Java 
> code to enable the HttpClient cache to persist, but our initial suspicion is 
> that doing that would be risky and confusing and potentially not work anyway, 
> because it's really like a browser, it doesn't necessarily just use the 
> cached copy if the remote one is unavailable, at least not predictably.

a) could be improved by a helper process that refreshes a set of 
'favorite' entities proactively without waiting for a further user 
access or timeout to keep these favorites fresh.

The set of favorites could either be configured or dynamically be 
maintained based on actual repetitive entity usage over some period.

Such an approach could reduce the risk for important entities that are 
not used every day and make b) unnecessary.

Thomas

--
SWITCH
------
Thomas Lenggenhager
P.O. Box, 8021 Zurich, Switzerland
phone +41 44 268 1505  direct +41 44 268 1541
https://www.switch.ch