Date: Tue, 19 Mar 2024 10:30:50 +0100 (CET) Message-ID: <180158692.5301.1710840650111@wiki01p.surfnet.nl> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_5300_37821773.1710840650111" ------=_Part_5300_37821773.1710840650111 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Entity Categories group federation entities that share common criteri= a. Entities (Identity Providers and Service Providers) can declare in their= metadata to which Entity Categories they belong. This must be reviewed and= approved by the federation the entity belongs to.
The goal of Entity Categories is to allow Identity Providers to release = their attributes more easily to a group of Service Providers, instead of ea= ch individual Service Provider. In the latter case, the Identity Provider h= as to review each Service Provider separately, which costs a lot of time. W= ith Entity Categories, the Identity Provider automatically= releases attributes to the entire group at once.
Currently, these are the most popular Entity Categories used within eduG= AIN:
Official URL: https://refeds.org/categor= y/research-and-scholarship/
Candidates for the Research and Scholarship (R&S) Category are Servi= ce Providers that are operated for the purpose of supporting research and s= cholarship interaction, collaboration or management, at least in part.
Example Service Providers may include (but are not limited to) collabora= tive tools and services such as wikis, blogs, project and grant management = tools that require some personal information about users to work effectivel= y. This Entity Category should not be used for access to licensed content s= uch as e-journals.
As a Service Provider, you must select a subset of the following attribu= tes for this entity category:
SURFconext must review your application to this entity category. If you = would like to join this category, please contact support@surfco= next.nl.
Official URL: https://refeds.org/category/code-of-= conduct
As a Service Provider, to declare you have signed the = Code of Conduct (in short: affirm that you are compliant with the GDPR)= , you can include the Code of Conduct Entity Category in your metadata. Ple= ase follow the link above to see what changes you must make to your metadat= a.
Official URL: https://refeds.org/category/hid= e-from-discovery/
In some federations, test and production ent= ities are mixed up in the same federation. In that case, it might happen th= at test Identity Providers are published into eduGAIN. Usuall= y, it's not the intention to include those entities on the discovery page o= f a Service Provider. Therefore, the Hide from Discovery category was estab= lished. Identity Providers that are part of this category wish not to be sh= own on a discovery page (WAYF). As a Service Provider, you must adapt your = discovery page to adhere to this wish.
Within SURFconext, test entities are part of another (test= ) federation. SURFconext doesn't publish any test entities in= to eduGAIN, so it is very unlikely an Identity Provider in SURFconext shoul= d become part of this entity category. If for whatever reason you would lik= e to become part of this entity category, please look at the URL above to s= ee what changes you must make to your metadata.
Official URL: https://refeds.org/sirtfi
Entity is compliant with the Security Incident Response Trust Framework = for Federated Identity. See Sirtfi and SURFconext