Changes between Version 33 and Version 34 of ServiceProviderFederation


Ignore:
Timestamp:
11/14/16 10:35:21 (8 years ago)
Author:
Dieter Van Uytvanck
Comment:

removed attribute requirements per SP - should be kept in SAML metadata

Legend:

Unmodified
Added
Removed
Modified

  • ServiceProviderFederation

    v33 v34  
    5858Is there a policy for what should be used as the unique ID? No.
    5959
    60 
    6160=== SURFconext ===
    6261
    … …  
    8281=== Attribute release ===
    8382
    84 * [http://www.clarin.eu/page/3578 older overview]
    8583* [https://lindat.mff.cuni.cz/secure/attributes.xml automatically produced, current overview]
     84* [http://www.clarin.eu/page/3578 older (outdated, manually maintained) overview]
    8685
    8786== Attributes requested by SPF services ==
    8887
    89 These should be listed in the SAML metadata about the SP.
     88These should be listed in the SAML metadata about the SP - see recommendation 8 (attributeconsumingservice) of https://www.clarin.eu/content/guidelines-saml-metadata-about-your-sp
    9089
    91 === [[Component Registry]] ===
    92 
    93  * strictly required: ePPN
    94  * nice to have: displayName, cn (common name)
    95 
    96 === [[Virtual Collection Registry]] ===
    97 
    98  * strictly required: eduPersonTargetedID (could also be configured to work with ePPN)
    99  * nice to have: cn, displayName
    100 
    101 === WebLicht ===
    102 
    103  * strictly required: (no attributes - as not all IdPs are releasing anything useful)
    104  * nice to have:
    105 
    106 === TQE (CLARIN-NL, http://hdl.handle.net/1839/00-SERV-0000-0000-0005-6) ===
    107 
    108  * strictly required: (no attributes)
    109  * nice to have: (no attributes)
    110 
    111 === Adelheid anntool ((clarin-nl, http://hdl.handle.net/1839/00-SERV-0000-0000-0005-6) ===
    112 
    113  * strictly required:
    114  * nice to have:
    115