Information Mediator Working Group Meeting

Meeting Day/Time: Wednesdays at 1300 UTC

Review affiliations

Move future scope to Readme or Confluence

@Tõnis Pihlakas wondering about API authentication
1. Keycloak
2. Trust services: authentication services - ID.ee
3. GitBook - Ramkumar points to this doc to explain the auth/api gateway strategy.

Taylor to add auth convo to tech committee

Ramkumar to add comments to GitBook spec before next week

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

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
Tõnis' proposed changes/comments for the spec

@Aleksander Reitsakas and Tõnis to draft service API and present to Taylor and Ramkumar at next meeting

Review BB spec issues: IM-28: Update Information Mediator Specification for Version 1.0 releaseDone; tag those that require technical knowledge; tag those that do not and can be handled by a tech writer. @Aleksander Reitsakas