Page History
...
Based on prior work by RENATER the international Identity Federations community (lead by Internet2, REFEDS and GEANT/eduGAIN) has started to create Service Categories (technically called "Entity Categories", since they apply to SAML "entities") in order to ease the management of release of personal data ("attributes") to services: It has long been apparent that manually writing and maintaining attribute release rules based on individual services does not scale sufficiently, esp. taking into account that science and e-research today requires international collaboration and does not stop at national or "federation" borders. Dealing with individual services on a case-by-case basis creates too much work for institutions and their staff (if done "right"), often resulting in students or scientists scholars not being able to access needed (inter-)federated resources because the institiutional SAML Identity Provider did not release any data to the accessed service.
| Info | ||
|---|---|---|
| ||
Entity Categories solve this problem by grouping related services into clearly defined categories (taking into account purpose, risk/benefit and legal requirements) and scaling the management of those categories (i.e., which services are part of which category) across Identity Federations. |
...
Membership in this category https://refeds.org/category/research-and-scholarship/ is reserved to services "that support research and scholarship interaction, collaboration or management as an essential component.". This globally applicable category takes a risk-based approach , to enabling access to high-benefit resources with /low-risk services, releasing only low-risk personal data. Basically only the minimum personal data required for scientific collaboration and attribution of a person's work (name, email address and an identifer) is releasedis released.
| Info | ||
|---|---|---|
| ||
REFEDS R&S is purpose- and attribute limited: Only services fitting the purpose requirements may apply, and those services may only request a limited set of low-risk attributes. It is being used gobally. |
| Expand | |||||
|---|---|---|---|---|---|
| |||||
|
...
GEANT EU/EEA Data Protection Code of Conduct
As part of the Code of Conduct Cookbook you'll find the Recipe for a Home Organisation, giving complete instructions on the necessary steps for deployment. This Service Category only applies when both the Service Provider and the Identity Provider are based in the EU/EEA (i.e., it does not help with services outside the EU/EEA) and takes a rather literal reading of the EU data protection directive (as common frame for disparate implementations thereof throughout the EU). As such it is mostly meant as a reminder and a reassurance to both service owners and home organizations that the services covered are already subject to (national implementations of) EU data protection law.
| Info | ||
|---|---|---|
| ||
GEANT Data Protection Code of Conduct legislation-limited: Only services from specific legislations (EU/EEA or "equivalent") may carry this category, and only if they correctly submit themselfs to the Code of Conduct and its requirements. |
As this Category definition does not specify an attribute bundle (i.e., it doesn't reference specific attributes which should be released) the list of attributes to release is basically open-ended. As such you may need to adapt the attribute rules included within
...
the example policy produced below, possibly including more (or fewer) attributes
...
if you have those available in your IDP
...
. The confguration below is an example based on the most commonly used attributes in Identity Federations today which
...
most/all
...
eduID.at Identity Providers should be able to generate.
| Expand | |||||
|---|---|---|---|---|---|
| |||||
|
Overview
Content Tools
Tasks