Skip to Content.
Sympa Menu

per-entity - Re: [Per-Entity] implementing a cache on the client

Subject: Per-Entity Metadata Working Group

List archive

Re: [Per-Entity] implementing a cache on the client


Chronological Thread 
  • From: David Walker <>
  • To: "Cantor, Scott" <>, "" <>
  • Subject: Re: [Per-Entity] implementing a cache on the client
  • Date: Thu, 4 Aug 2016 13:30:32 -0700
  • Authentication-results: spf=none (sender IP is ) ;
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:99

Agreed that it's really just a couple of minutes.  My point was that any change is viewed as "significant" to many system administrators.  The thing going for us is that, ultimately, doing nothing is not an option.

David


On 08/04/2016 01:19 PM, Cantor, Scott wrote:
*	IdP and SP administrators will need to do something to take
advantage of per-entity metadata distribution.  Even assuming we don't ask
them (or their institutions) to run the distribution layer, they still have
significant work to do.
I would not agree that a few config changes is significant work. Getting people to do it is a hassle, but that's not because it's hard, it takes a couple of minutes to do the change. If you're thinking in terms of some kind of large scale testing activity by every site, we can't go into this with that expectation.

The most significant work would be if we change the signing key, but that's work "in theory" since in practice people don't carefully validate trust anchors just because they should.

*	If we did ask them to run their part of the distribution layer, we could
provide them with an instrumented VM container.
Still a non-starter IMHO. What you'd have to do is force us to built it into the software, essentially.

-- Scott


Attachment: signature.asc
Description: OpenPGP digital signature




Archive powered by MHonArc 2.6.19.

Top of Page