Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  1. When a working group is agreed, REFEDS Participants will be asked if they wish to participate. Working Groups tend to be small, so consensus can be achieved quickly between participants.
  2. A chair for the group is chosen from the REFEDS Participants.
  3. GEANT provides facilities for the working group, including meeting support, wiki space, mailing lists and, where appropriate, funding.
  4. An appropriate output from the group is produced. Currently, this is typically a draft white paper or a wiki page.
  5. When the Working Group is in agreement, the chair shares the outputs with the wider REFEDS community with an open period for discussion and comment. This is typically a period of 4 weeks, but may be longer if appropriate.
  6. After this period of time, the REFEDS Steering Committee signs off on the work item. Work is either written up as a formal white paper, left on the wiki but promoted as finished work or occasionally submitted as an Internet Draft.


Niels van Dijk (SURFnet)

Work Items

Ideas for work items for the group:

OIDC profile for eduPerson attributes

OpenID Connect (OIDC) offers an Authentication protocol similar to SAML. Many of the participants in REFEDs use the well know eduPERSON and SCHAC schema to express attributes when using SAML
OIDC has a similar ability, with the use of claims. A standard set of claims is defined by OIDC, however this set is not compatible with eduPERSON and SCHAC.

To effectively use OIDC in R&E it would be nice if some guidelines would exist how to deal with this difference.

This activity investigates the best way to deal with the differences between definitions in attributes and claims. Next to participants from REFEDs the activity will try to engage relevant parties including MACE-DIR, SCHAC and OIDC standardisation bodies


Planning spreadsheet:  

Notes from EWTI:$mappingedupersonto.

Mailing list:

GitHub space:

Scope, Activities and planning