Skip to Content.
Sympa Menu

edugain-discuss - [eduGAIN-discuss] SPs with no attribute requirements (or so it seems)

edugain-discuss AT lists.geant.org

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

List archive

[eduGAIN-discuss] SPs with no attribute requirements (or so it seems)


Chronological Thread 
  • From: Niels van Dijk <niels.vandijk AT surfnet.nl>
  • To: edugain-discuss AT geant.net
  • Subject: [eduGAIN-discuss] SPs with no attribute requirements (or so it seems)
  • Date: Thu, 27 Mar 2014 11:13:16 +0100
  • List-archive: <https://mail.geant.net/mailman/private/edugain-discuss/>
  • List-id: eduGAIN discussion list <edugain-discuss.geant.net>

Hi all,

I am wondering what to do with an eduGAIN SP that has no attribute
requirements in the metadata.

eduGAIN policy states:
(http://www.geant.net/service/eduGAIN/resources/Documents/eduGAIN_metadata_profile_v3.doc)

"NOTE on <md:RequestedAttribute>: Whenever a Service Provider needs
attributes it should list them as <md:RequestedAttribute> in the
<md:AttributeConsumingService> of its <md:SPSSODescriptor> element to
increase the chance that Identity Providers really release them."

Based on the above I assume that I can connect to this SP not releasing
any attributes. However, the note is a bit ambiguous:
- It does not state "MUST list them"
- It spells "should" and not "SHOULD" as defined per RFC2119

What is expected behaviour from the IdP?

thanks!
Niels










Archive powered by MHonArc 2.6.19.

Top of Page