InCommon metadata support

[Christopher Bongaarts <>]

On 1/23/2014 10:36 AM, Tom Poage wrote:
> On Jan 21, 2014, at 2:26 PM, Tom Scavo
> > >At this point, only the site administrators have been contacted but
> > >your point is well taken. Perhaps we should reach out to all technical
> > >contacts in metadata as well? Would this help?
> > >
> > >What do others think about contacting all technical contacts in metadata?
> I think part of the answer depends on the typical number of IdPs federating 
> with most SPs.
>
> If the typical SP is someone's homegrown app and only used by one or two 
> IdPs, perhaps it makes sense for IdP operators to contact them directly. 
> Larger SPs--those federating with numerous IdPs--would incur some overhead of 
> being contacted numerous times by each IdP operator, not to mention aggregate 
> effort of N IdPs contacting M SP operators (NxM).

My opinion (which should not be weighted too highly as my institution 
does not have any SPs registered yet) is that SPs that are interested in 
keeping up with this sort of thing should subscribe to the InCommon ops 
list.  If an institution registers an SP themselves, they can take 
responsibility for passing along the notifications if the SP operator 
chooses not to subscribe.  An institution could choose, as part of 
registering an SP with InCommon, to recommend that the SP operator 
subscribe to the ops list.

No need for broadcasting to all contact addresses - those should be used 
for more targeted communications (e.g. "Your specific SP has a 
particular problem, please fix").

--
%%  Christopher A. Bongaarts   %%  

          %%
%%  OIT - Identity Management  %%  http://umn.edu/~cab  %%
%%  University of Minnesota    %%  +1 (612) 625-1809    %%