Skip to Content.

edugain-discuss - Re: [eduGAIN-discuss] Filtering eduPersonEntitlement

edugain-discuss AT lists.geant.org

Subject: An open discussion list for topics related to the eduGAIN interfederation service.

List archive


Re: [eduGAIN-discuss] Filtering eduPersonEntitlement


Chronological Thread 
  • From: Peter Schober <peter.schober AT univie.ac.at>
  • To: edugain-discuss AT lists.geant.org
  • Subject: Re: [eduGAIN-discuss] Filtering eduPersonEntitlement
  • Date: Fri, 22 May 2020 11:07:03 +0200
  • Organization: ACOnet

* Peter Schober <peter.schober AT univie.ac.at> [2020-05-22 10:37]:
> > However, it doesn't look like there are any examples of this in
> > eduGAIN metadata
>
> In this case that's because you (the UK federation) are publishing
> all of those SPs into eduGAIN already, but without that information
> present.

To go beyond merely stating why there are no such examples in eduGAIN:

This case (though there are others) is a good examlpe that we as the
eduGAIN community should think about whether it makes sense to
establish a "best copy of metdata in eduGAIN" practice, not merely a
"first one wins".

I.e., maybe its time to agree on what the ideal metadata for any given
service should look like (one that can possibly accommodate even
diverting practices across federations and institutions) and promote a
practice of amending the metadata published into eduGAIN to become
closer to that ideal.
(So this is not about changing the eduGAIN MDS algorithm for selecting
a copy from multiple federations for publication, this is about
getting the metadata amended at the current "home federation".)

RequestedAttribute elements are certainly one such case, but given the
number of SPs in eduGAIN that don't even have a display name (of any
kind, e.g. md:ServiceName or mdui:DisplayName) or description set, the
current state of affairs is rather sorry, IMO.

-peter



Archive powered by MHonArc 2.6.19.

Top of Page