Skip to Content.

edugain-discuss - Re: [eduGAIN-discuss] Test/dev IdPs in eduGAIN metadata

edugain-discuss AT lists.geant.org

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

List archive


Re: [eduGAIN-discuss] Test/dev IdPs in eduGAIN metadata


Chronological Thread 
  • From: Tom Scavo <trscavo AT internet2.edu>
  • To: Olivier Salaün <olivier.salaun AT renater.fr>
  • Cc: "edugain-discuss AT geant.net" <edugain-discuss AT geant.net>
  • Subject: Re: [eduGAIN-discuss] Test/dev IdPs in eduGAIN metadata
  • Date: Thu, 16 Apr 2015 09:02:32 -0400
  • Authentication-results: prod-mail.geant.net (amavisd-new); dkim=pass header.i= AT gmail.com
  • List-archive: <http://mail.geant.net/pipermail/edugain-discuss/>
  • List-id: "An open discussion list for topics related to the eduGAIN interfederation service." <edugain-discuss.geant.net>

On Thu, Apr 16, 2015 at 7:57 AM, Olivier Salaün
<olivier.salaun AT renater.fr> wrote:
>
> Actually why do federation include such test IdPs in their eduGAIN upstream
> metadata?

I don't think that's a valid conclusion. An IdP that is tagged
"hide-from-discovery" is (or should be) exactly what the spec says it
is, nothing more.

> Are their real use cases?

For exporting a "hide-from-discovery" IdP to eduGAIN? Sure. Suppose an
IdP registers with a federation to facilitate B2B (i.e., vendor)
interactions only. That IdP is neither willing nor able to handle
requests from arbitrary SPs, only those SPs for which it is has a
contract in place.

> Any chance these test IdPs would be removed from upstream eduGAIN metadata?

I don't think this is an eduGAIN issue nor is this a
"hide-from-discovery" issue. You seem to be talking about something
else altogether.

Tom





Archive powered by MHonArc 2.6.19.

Top of Page