Information Mediator Working Group Meeting

Meeting Day/Time: Wednesdays at 1300 UTC

Meeting Link: Jitsi Meet

Wednesday, March 29th, 2023

Attendees:

1. @Taylor Downs

2. @Aleksander Reitsakas

3. Ramkumar

Agenda

Next Steps & Action Items

Wednesday, March 22nd, 2023

Attendees:

1. @Taylor Downs

2. @Tõnis Pihlakas

3. Ramkumar

Agenda

1. @Tõnis Pihlakas wondering about API authentication

   1. Keycloak

   2. Trust services: authentication services - ID.ee

   3. https://app.gitbook.com/o/pxmRWOPoaU8fUAbbcrus/s/39QVhd0jD6S29Isr7KGF/architecture-and-nonfunctional-requirements/6-onboarding#6.2-api-gateways - Ramkumar points to this doc to explain the auth/api gateway strategy.

Action Items

Wednesday, March 1st, 2023

Attendees

1. Aleksander

2. Tõnis

3. Taylor

4. Ramkumar

Team Focus

We need to define service APIs so we can validate candidate applications to play the role of Information Mediator.

Agenda

1. API for Registering Members/Applications with the IM

   1. @Taylor Downs “Are there two different applications with two different APIs that must be defined? The central-server and the security-server?”

   2. For the purposes of this conversation, we assume that a central-server has already been deployed and a security-server is already running and in communication with that central server. Now we discuss adding a member to that security server and registering applications/services.

   3. If a member has been registered with a central-server , the security-server should provide an API which allows you to add/enable that member on the security-server.

      1. post to /api/members with << WHAT DETAILS >> in order to register a new member with the IM

2. Tõnis' proposed changes/comments for the spec

Next Steps

Old Meeting Notes

• IM Past Meeting Note

• 20.04.2021- Meeting Note

•