...

1. Simple mapping based on mapping well understuud attributes (name, mail, sub)
2. Advanced mapping, mapping commonly used attributes from eduPERSON, SCAHC and eduMEMBER. Register these in the IANA JSON Web Token Claims registry.
3. Investigate the mapping of the R&S bundle in OIDC (just the attributes, not the trust framework)

OIDC Federation

...

The OpenID Connect Federation work is carried out with help of the GN4-2 project:
See also https://wiki.geant.org/display/gn42jra3/T3.1A+OpenID+Connect+Federation

1. A first version of the OIDCfed test suite is up and running

2. Roland has working federation aware RP and OP implementations for internal use.

3. Ioannis and Andres is working on a federation aware OP (based on pyoidc) for people how want to run their own.

4. Andreas is adding federation awareness to a OIDC NodeJS library

5. Janusz is adding federation awareness to a OIDC PHP library

6. Janne&Henri is working adding OIDC functionality to Shib together with the Shib dev team.

7. An update to the OIDC federation draft to be released in a couple of weeks.

8. Herve, Jule and Maarten are interviewing federations ons there plans, requirements and use-cases.
   
   

Planning

SAML to OIDC mapping

...

1. Simple mapping document to be delivered for public consutation at REFEDs no later then May 29, 2017
2. Advanced mapping document to be delivered for public consutation at REFEDs no later then May 29, 2017. Registation in the IANA JSON Web Token Claims registry thereafter, but no later then Dec 31, 2017.
3. Report on mapping of the R&S bundle in OIDC to be delivered by Sept 1 2017

OIDC Federation

-- INput from Roland here--First round of work to be done early June.