Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 2 Next »

Attendees

Apologies

Agenda

Presenter

Duration

Discussion

Technical Reviews of BB specs

Steve Conrad

10 minutes

Architecture team to review Wave 3 specifications:

Decoupling BBs

Steve Conrad

15 minutes

How do we handle large DPGs as BB candidates?

Capabilities/Service Blocks

Wes Brown

15 minutes

Review service block (capabilities) template

GERA Update

Aare Laponin PSRAMKUMAR

15 minutes

Update on changes to GERA document and progress/next steps

Next steps/AOB

Steve Conrad

5 minutes

What should we prioritize?

Future topic - Fall 2023

Manage Access Authorization to BB APIs

Jaume DUBOIS

30 minutes

  • Types of accessors checked (human, back-end systems, apps or browser, robots, hardware, ..)

  • Granularity of access control (Building block, module, API, single API service, single API service for specific tenant or data)

From Technical Committee Meeting:

BBs should not own RBAC - the calling applications are responsible for it. 

Are we using token based authorization within the request to BB?

How to get candidates bypass its own RBAC?

  1. Superuser access to be given when merging with IM backend?

  2. Or control to switch off existing RBAC in target BBs

  3. option to have api token registered in IM at max permission level for specific member entities

  4. come up with a concrete example for this case

Action Items

  • Ramkumar to connect with Hani/Nico on infra requirements

  • Ramkumar/Steve to meet with Vasil

  • Arch team members to review UX Switching document: UX Switching

Future Topics

  • Define a standard set of APIs that are needed for any BB to indicate that they are running, configured and ready to use in the sandbox (or test harness). Do we need a BB registry?

  • No labels