edugain-discuss AT lists.geant.org
Subject: An open discussion list for topics related to the eduGAIN interfederation service.
List archive
- From: Peter Schober <peter.schober AT univie.ac.at>
- To: edugain-discuss AT geant.net
- Subject: Re: [eduGAIN-discuss] Locations for 'local' eduGAIN metadata
- Date: Mon, 12 Jan 2015 14:20:10 +0100
- Authentication-results: prod-mail.geant.net (amavisd-new); dkim=pass header.i= AT univie.ac.at
- 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>
- Organization: ACOnet
Hey,
Lukas has given you the closest to what you're probably after.
Some more general remarks on the process:
* Niels van Dijk <niels.vandijk AT surfnet.nl> [2015-01-12 13:38]:
> I'm setting up 2 services for eduGAIN. As part of my documentation I
> would like to point the IdPs to the 'local' eduGAIN metadata feed of
> their national federation, which should at some point will contain the
> metadata of my services.
Since those IDPs are members of their local federation, they should
know where to find their own federation's SAML metadata or
documentation or support channel(s), no?
I wouldn't want any SP to join eduGAIN having to explain to any/all
IDPs from my own federation how our federation works or where/how to
securely use our metadata.
If this is about IDPs not yet in eduGAIN (i.e., federations not having
adopted an opt-out regime yet) I think all you should do is tell them
to talk to their local federation operator -- and probably also cc:
the fedop concerned.
If the IDPs are exposed to eduGAIN already, OTOH, there should be
nothing left to do (unless the IDP is broken and does not itself
consume eduGAIN-enabled metadata, which I'd accept as an error report
to the fed. operator).
My 2¢.
-peter
- [eduGAIN-discuss] Locations for 'local' eduGAIN metadata, Niels van Dijk, 12-Jan-2015
- Re: [eduGAIN-discuss] Locations for 'local' eduGAIN metadata, Lukas Hämmerle, 12-Jan-2015
- Re: [eduGAIN-discuss] Locations for 'local' eduGAIN metadata, Peter Schober, 01/12/2015
- Re: [eduGAIN-discuss] Locations for 'local' eduGAIN metadata, Mikael Linden, 12-Jan-2015
- Re: [eduGAIN-discuss] Locations for 'local' eduGAIN metadata, Nicole Harris, 12-Jan-2015
- Re: [eduGAIN-discuss] Locations for 'local' eduGAIN metadata, Chris Phillips, 12-Jan-2015
- Re: [eduGAIN-discuss] Locations for 'local' eduGAIN metadata, Nicole Harris, 12-Jan-2015
- Re: [eduGAIN-discuss] Locations for 'local' eduGAIN metadata, Peter Schober, 12-Jan-2015
- Re: [eduGAIN-discuss] Locations for 'local' eduGAIN metadata, Niels van Dijk, 12-Jan-2015
- Re: [eduGAIN-discuss] Locations for 'local' eduGAIN metadata, Ian Young, 12-Jan-2015
- Re: [eduGAIN-discuss] Locations for 'local' eduGAIN metadata, Niels van Dijk, 13-Jan-2015
- Re: [eduGAIN-discuss] Locations for 'local' eduGAIN metadata, Nicole Harris, 13-Jan-2015
- Re: [eduGAIN-discuss] Locations for 'local' eduGAIN metadata, Peter Schober, 13-Jan-2015
- Re: [eduGAIN-discuss] Locations for 'local' eduGAIN metadata, Ian Young, 12-Jan-2015
- Re: [eduGAIN-discuss] Locations for 'local' eduGAIN metadata, Niels van Dijk, 12-Jan-2015
- Re: [eduGAIN-discuss] Locations for 'local' eduGAIN metadata, Chris Phillips, 12-Jan-2015
- Re: [eduGAIN-discuss] Locations for 'local' eduGAIN metadata, Nicole Harris, 12-Jan-2015
Archive powered by MHonArc 2.6.19.