You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Date

Attendees

Goals

  • Development: where are we?
  • Technical Setup for the pilot
  • Dig down the pilot use cases

Discussion items

TimeItemWhoNotes
30minDevelopment
  • Meeting at techex:

    • Shibboleth dev team is happy about the code, just minor remarks.

    • Great interest from the shib users community at techex
  • Working on right now:
    • Dynamic registration just started
    • Implementing suggestions from shib dev team for the configuration
  • What will be probably ready for the Hackathon:
    • Implicit flow

  • Work on the auth code grant flow will start end of the year/beginning next one
 30min Technical Setup for the pilot
  • https://github.com/OpenIDC/fedoidc is a good testing platform for developers, but not suitable for the pilot
  • partners should be given a simple-to-install environment to participate to the pilot
  • automation: fedoic can be used to fire up a ready-service based on vagrant or docker
  • a simple open OP with self-service user sign up should be added to the suite

Alejandro Pérez Méndez and Davide Vaghetti can start working on the automation for fedoid deploy — other team members are welcome!

30min

Pilot use cases

Use cases will focus more on the federation aspects, rather than on the strength of OIDC as a protocol.

At least three use cases can be envisioned from the federation point of view:

1. Simple hierarchy with a global fedop as root

 Federation → NREN → OP/RP    

2. Hierarchy with NREN as root

 NREN → OP/RP

3. Hierarchy with local entity as root

 UNIVERSITY→ OP/RP

For the RP/service part a simple hello world application should be sufficient, but a better one could be a hello world MOBILE app.

Action items

  • No labels