Skip to Content.
Sympa Menu

edugain-discuss - Re: [eduGAIN-discuss] [refeds] mari plan & next steps

edugain-discuss AT lists.geant.org

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

List archive

Re: [eduGAIN-discuss] [refeds] mari plan & next steps


Chronological Thread 
  • From: Peter Schober <peter.schober AT univie.ac.at>
  • To: REFEDS <refeds AT terena.org>, "edugain-discuss AT geant.net" <edugain-discuss AT geant.net>
  • Subject: Re: [eduGAIN-discuss] [refeds] mari plan & next steps
  • Date: Wed, 29 Oct 2014 17:26:59 +0100
  • Authentication-results: prod-mail.geant.net (amavisd-new); dkim=pass header.i= AT univie.ac.at
  • List-archive: <https://mail.geant.net/mailman/private/edugain-discuss/>
  • List-id: eduGAIN discussion list <edugain-discuss.geant.net>
  • Organization: ACOnet

* Leif Johansson <leifj AT sunet.se> [2014-10-29 15:48]:
> <RequestedAttribute
> NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:meta" Name="foo" />
>
> which requests release of the 'foo' attribute, the IdP releases one
> or more "regular" oid-based attributes on the wire which corresponds
> to 'foo' according to the accepted practice of the IdP.

Btw, how would that affect REFEDS R&S attribute requirements?
Would those be changed to speak about the required meta-attributes,
too, instead of about specific attribute names?

I'd prefer to keep those attribute requirements concrete, in order to
stimulate harmonization. (You only satisfy/support REFEDS R&S if you
request/provide exactly those attribute names.)

And if so, shoudn't Entity Categories with attribute bundles solve
that same problem? So we're now going back a step trying to revive
RequestedAttributes?
Well, we're not restricted to one only appraoch, I guess.
-peter





Archive powered by MHonArc 2.6.19.

Top of Page