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 6 Next »

Attendees

Apologies

Agenda

Presenter

Duration

Discussion

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)

Management of UX switching

PSRAMKUMAR

Steve Conrad

10 minutes

Review synchronous and async flows for UX switching. Review self-service and agent-led workflows as well.

Documentation from Ramkumar: UX Switching

Architecture team to review and provide feedback.

  • 3 options are outlined - should we make a recommendation as to which approach is preferred?

    • OIDC is called out in the cross-BB auth as well

Infrastructure APIs

Steve Conrad

Vasil Kolev

20 minutes

  • Plugin API for BBs - related to service discovery, portal integration, infrastructure management, use case deployment and overall user experience once presented with the portal UI to manage what we are offering.

    • Portal application showing use cases available in the sandbox, allowing users to swap out BBs

    • Need APIs to determine what BBs are available, whether they are ready/running.

    • Define a standard set of APIs that are needed for any BB (arch team)

    • Do we need a BB registry?

In Sandbox, if we want to run multiple instances of a BB (giving user ability to swap out BBs), we need to have a mechanism to map the IP/URL/endpoints of the new BB.

What is needed for a ‘general GovStack’ implementation vs what is specific to Sandbox.

Next steps/AOB

Steve Conrad

5 minutes

What should we prioritize?

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