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

Compare with Current View Page History

« Previous Version 2 Next »

Minutes

Only specific points raised and queries are minuted - see slides for what is presented.

Session 1: Planning Reports

Task 1 - Campus and Fed

Campus IdP Challenges - non technical, process and business challenges.

  • Experience from FaaS - the trust relationship between the campus and GÉANT is a gap.
  • Scope - IdP or IDM?
  • Link to eduroam-as-a-Service.
  • Sustainability
  • What do established federations benefit from this?

SIRTFI Challenges

  • Coordination with several bodies - AARC, GÉANT, REFEDS.
  • How to get high coverage without 'mandatory' which results in expulsion from eduGAIN.

Task 2 - Research & SP

e-Science Support

  • Use existing OTRS/ticketing system and escalation concepts
  • REFEDs also able to feed it in
  • Think about scaling the support depending on user types.
  • eduroam used scripts to direct queries too

Assurance

  • Needs some refining on workplan decisions
  • Lots of options, not clear info
  • VO PaaS requires some assurance info - good location for the tool as a context provider.
  • Suggest working on improving federation documentation in this field.
  • Who implements the tool? AARC or GÉANT? (We have budget and dev)

Additional work items

  • Various check tools nearly all have connections with other tasks
  • wiki.edugain.org - should this move to new wiki system?
  • TODO - reusing information from the wiki to be real support docs for different target users

Task 3 - TrustTech

User centric ID

  • Question - is there a link between user centric ID and Campus IdP - should small countries jump straight to user-centric if they don't have a footprint? M18 should trigger a decision?

MFA

  • MFA service in VO context? (Surfnet model)
  • Who 'triggers' the requirement? SP, IdP, User?
  • Beware vendor lock-in.

Mobile

  • Gap - mobile phone usability for IdP dialog windows
  • ECP?

Cross sector

  • Link with VO PaaS
  • SaToSa aspects are only once VOPaaS is complete with it's development of it

 

Action items

  •  
  • No labels