Participants

Agenda

Recording Notice

Notice: This video call will be recorded solely to assist in preparing notes. The recording will be used internally for this purpose only and will not be shared with anyone outside of this context.

Agenda Overview

Approval of minutes from the previous WG meeting

Actions

Meeting Overview

• The first meeting of 2025 for the EOSC Architecture Working Group focused on discussing recent developments in the EOSC ecosystem.
• Integration of services through EOSC nodes and planning the group's work for the coming year were key topics.

Stakeholder Interviews Presentation

Marina and Janos may be able to present the status of stakeholder interviews at the next meeting.

The stakeholder interviews are expected to provide valuable input from a general perspective for requirements on the AAI

Winter School Update

• The EOSC Winter School event took place the previous week, focusing on the EOSC Federation.
• Discussions at the Winter School covered interoperability, sustainability and other themes relevant to the EOSC Opportunity Areas.
• On the AAI topic, participants pointed out that we should be using and updating as necessary the EOSC AAI architecture, leveraging eduGAIN and using MyAccessID as a common researcher identity across EuroHPC and EOSC.

• The EOSC Association is working  to prepare an informal paper in the coming two weeks to inform the European Commission about upcoming calls at the European level. This paper aims to align these calls with the EOSC Multi-Annual Roadmap (MAR) 2026–2027 

EOSC Nodes Updates - Current status

• There is significant interest from DG RTD to proceed with the integration of service nodes.
• The process selecting candidate nodes, including national, thematic, and regional nodes, is ongoing.
• Meetings are being organised with each node to assess readiness and discuss integration plans.
• The timelines are pressing and this puts pressure also on the EOSC AAI for tangible plans on how the integration can start.

Building up the EOSC Federation

• Services will not be directly connected to the EOSC Federation but will connect through nodes (national, thematic, or regional).
• The group discussed the possibility of services connecting to multiple nodes, weighing the benefits and complexities of such an approach.
• Three options for service/node integration were proposed: Connect individual services directly to the EOSC EU node, connect nodes to the same trusted route (e.g., using MyAccessID), and implement a full mesh connection between nodes (more complex setup).
• The group debated the practicality and scalability of these options, considering the expected number of nodes (around 10 working by summer).

We need to update the EOSC AAI Architecture v2022

• Each user MUST have the possibility to use one identity across all EOSC Nodes / Services. This principle aligns with the AARC Blueprint Architecture but allows for the possibility of multiple identities if desired.
• Introduction of the Node concept (but not spend time defining what a Node is)
• Services are NOT connected directly to the EOSC Federation. They are connected via the EOSC Nodes.
• Should services be connected to multiple nodes?
• We should differentiate between connection and findability
• OpenID Connect must be the primary intra-federation protocol.

Team working on the AAI Architecture v2025

• A small team will be formed to work on these updates, meeting weekly and reporting back to the larger group.
• The updated document will build upon the existing Federation Paper and Architecture 2022 document, restructuring and updating the mechanics around new flows.
• Members were asked to volunteer for this team, with final confirmation expected at the next meeting in one week.

• Interest for participation:
• Nicolas Liampotis (GRNET)
• Michal Stava (GEANT)

Next Meeting

• The next meeting is scheduled for 31 January 2025.

Action Items

AOB