Jra3 multi domain_user_applications_research_year_3_review_final

343 views
303 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
343
On SlideShare
0
From Embeds
0
Number of Embeds
7
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Jra3 multi domain_user_applications_research_year_3_review_final

  1. 1. Joint Research Activity 3 (JRA3): Multi-Domain User Applications ResearchLicia Florio, TERENA Year 3, EC GN3 Review Brussels, June 2012 connect • communicate • collaborate
  2. 2. JRA3: Multi-Domain User Applications Research ! JRA3 Overview ! Progress Update ! Year 4 Plan ! Summary and ConclusionsOverview Progress Y4 Plan Summary connect • communicate • collaborate 2
  3. 3. What is JRA3?Overview Progress Y4 Plan Summary connect • communicate • collaborate 3
  4. 4. The Vision Enabling collaboration and data sharing Enabling users to be online anytime anywhere JRA3 Enabling GN3 services deployment and compositionOverview Progress Y4 Plan Summary connect • communicate • collaborate 4
  5. 5. JRA3 Structure JRA3 15 NRENs participating T1: Roaming T2: Identity T3: GEMBus Developments Federations (±76 MM) (± 28MM) (± 69 MM) JANET, SWITCH RENATER RESTENA, NIIF, GRNET DFN, TERENA, CARNET, CESNET, NORDUNET, ARNES PIONIER, RedIRIS SURFnetOverview Progress Y4 Plan Summary connect • communicate • collaborate 5
  6. 6. JRA3 Manpower Usage Technology Management Watchbrief 15% 15% Standardisation 20% Development 50%Overview Progress Y4 Plan Summary connect • communicate • collaborate 6
  7. 7. Task 1: Roaming Developments T1: Roaming Enhance Standardisation Developments eduroam work Task Leader: Stefan Winter (RESTENA)Overview Progress Y4 Plan Summary connect • communicate • collaborate 7
  8. 8. Task 1, Year 3 Goals T1 Ease eduroam deployment Continue IETF WorkOverview Progress Y4 Plan Summary connect • communicate • collaborate 8
  9. 9. Achievement: Standardisation Work ! RFC RADIUS-over-TLS ready! !   RFC 6614 “Transport Layer Security (TLS) Encryption for RADIUS” !  This RFC makes significant changes to the RADIUS protocolOverview Progress Y4 Plan Summary connect • communicate • collaborate 9
  10. 10. Importance of the RFC EU Radius .nl .xx .be uni.nl uni.be X.509 certsOverview Progress Y4 Plan Summary connect • communicate • collaborate 10
  11. 11. Achievement: eduroam Configuration Assistant Tool (CAT) ! Welcome to CAT http://cat-test.eduroam.orgOverview Progress Y4 Plan Summary connect • communicate • collaborate 11
  12. 12. Why CAT? ! CAT = Configuration Assistant Tool !  To make eduroam easier for end-users !  To generate automated installers for users’ devices !  It can be used as a centralised service or it can be installed locally !  Also provides tools for eduroam administrators !  Multilingual sites ! CAT has been entirely developed in JRA3 T1Overview Progress Y4 Plan Summary connect • communicate • collaborate 12
  13. 13. How CAT Works User canselect their institution User now choose the installerOverview Progress Y4 Plan Summary connect • communicate • collaborate 13
  14. 14. Mobile CAT Cat InstallerOverview Progress Y4 Plan Summary connect • communicate • collaborate 14
  15. 15. Task 1, Year 4 Goals ! Start Working on eduroam Dynamic Discovery !   Within the IETF !   In real life (eduroam federations need to start testing) ! Publish production-quality release of eduroam CAT code !   Version 1.0 expected ! Improve authentication methods specifications in the IETF !   EAP types ! Start working to support a hotspot monitoring solution !   To check availability and quality of eduroam for end-usersOverview Progress Y4 Plan Summary connect • communicate • collaborate 15
  16. 16. Task 2: Identity Federations Implement T2: Identity Support inter- Enable SSO supports for Federations federation beyond Web groups Task Leader: Andreas Solberg (UNINETT)Overview Progress Y4 Plan Summary connect • communicate • collaborate 16
  17. 17. Task 2, Year 3 Goals Design Protocol for groups More Results on T2 “Beyond Web SSO” Expand FedLabOverview Progress Y4 Plan Summary connect • communicate • collaborate 17
  18. 18. Achievement: Protocol for Groups ! VOOT = Virtual Organization Orthogonal Technology !   A protocol to manage groups in a dynamic way !   It based on existing protocols !   It targets inter-federation use cases !   Completely developed within JRA3 T2 ! SURFnet plans to use VOOT in production, starting from summer 2012 ! More info and demos at: ! https://rnd.feide.no/category/voot/Overview Progress Y4 Plan Summary connect • communicate • collaborate 18
  19. 19. Why VOOT? Scenario: •  Users working on a project would like to use collaborative services •  Users would need to create a group for each applicationOverview Progress Y4 Plan Summary connect • communicate • collaborate 19
  20. 20. How VOOT Works? ! Create a group once, use it for all applications ! VOOT groups are managed independently from the identity federationOverview Progress Y4 Plan Summary connect • communicate • collaborate 20
  21. 21. Achievement: FedLab FedLab provides online tools to support Identity Federations and Services ! Entirely built by JRA3-T2 team FedLab allows services to test their configurations !   Before the service is entered into a production federation The website also offers: ! Best practice documents ! Aimed at developers https://fed-lab.org/Overview Progress Y4 Plan Summary connect • communicate • collaborate 21
  22. 22. How does FedLab Work? ! Step 1: register the metadata ! Step 2: verify connectivity ! Step 3: run all testsOverview Progress Y4 Plan Summary connect • communicate • collaborate 22
  23. 23. Achievement: OpenID Connect in FedLab ! Main addition: !  Test facility for OpenID Connect protocol !  First implementation of the specs! !  The team was also involved in the protocol specifications http://vimeo.com/38634031Overview Progress Y4 Plan Summary connect • communicate • collaborate 23
  24. 24. Achievement: Beyond Web SSO ! The task contributed to the Moonshot project: !  Aim to combine the RADIUS infrastructure (eduroam) with application-level authentication (SAML) !  This requires significant changes to the protocols –  Some of this work was done in Task 2 –  Standardisation ongoing within the IETF ! Testbed for non-Web application was delivered in Dec 2011Overview Progress Y4 Plan Summary connect • communicate • collaborate 24
  25. 25. Task 2, Year 4 Goals ! Finalise the integration of OpenID Connect in FedLab ! Continue work in the Discovery Area ! Finalise the work on VOOTOverview Progress Y4 Plan Summary connect • communicate • collaborate 25
  26. 26. Task 3: GEMBus Develop a Enable platform for T3: GEMBus service service composition deployment Task Leader: Pedro Martínez Juliá (Univ. of Murcia)Overview Progress Y4 Plan Summary connect • communicate • collaborate 26
  27. 27. Task 3, Year 3 Goals • Further Develop GEMBus Start GEMBus T3 Core Elements Cookbook preparationOverview Progress Y4 Plan Summary connect • communicate • collaborate 27
  28. 28. Why GEMBus? Others Groups Mng GEMBus New AuthN tools Application Monitoring tools NetworkOverview Progress Y4 Plan Summary connect • communicate • collaborate 28
  29. 29. Achievement: Greater Stability In Core Components ! Extended the ESB concept to a general “service bus” ! Each service can be plugged without depending on specific service platforms ! Stable Core ComponentsOverview Progress Y4 Plan Summary connect • communicate • collaborate 29
  30. 30. Status of the GEMBus Core Services Registry Repository Global registry not ready yet New Interface under development 50% 90% 0% 80% 100% STS Accounting Building Support for OAuth Composition engine Integrated in the main architecture Interface for services Need testing in ‘real world’Overview Progress Y4 Plan Summary connect • communicate • collaborate 30
  31. 31. Achievement: GEMBus Cookbook ! Defines core services and their interactions. ! Shows how to interact with core services and how to build a new service !Describes how to set-up a testbed environment.Overview Progress Y4 Plan Summary connect • communicate • collaborate 31
  32. 32. Task 3, Year 4 Goals ! Finalise developments of GEMBus core components ! Get feedback on the cookbook ! Get feedback from GEMBus “users” ! No end-users, but software developers ! Prepare the plan on how to continue GEMBus work beyond GN3Overview Progress Y4 Plan Summary connect • communicate • collaborate 32
  33. 33. Summary and Conclusions connect • communicate • collaborate 33
  34. 34. •  Excellent results •  To enhance existing achieved: services •  IETF RFC, CAT, •  eduroam •  VOOT •  eduGAIN •  GEMBus Year 3 Goals Exploring Met and New Exceeded technologies Value for Raising GN3 • By participating in Money profile international initiatives •  IETF, Kantara, OpenID•  Looking for solutions Connect to real use-cases •  To enable cross-boundary collaboration connect • communicate • collaborate 34
  35. 35. Questions?connect • communicate • collaborate

×