Attendees
Apologies
Agenda | Presenter | Duration | Discussion |
Follow up on ID/Auth questions | 30 minutes | Vasil to develop a document that outlines the core questions/implementation concerns that you have. From there, could you work with Smita and Trev to outline the flow/process that is needed so that we can identify any gaps in the BB specs or documentation. Propose to use this document as a baseline - ensure that it accurately frames the issues: Authentication and Cross-BB Authorization Question: Should we frame multiple approaches or design patterns? Additional Notes:
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?
| |
PAERA Update | 15 minutes | Update on changes to PAERA document and progress/next steps Aare has created Chapter 4. This chapter will be finalized next week and the architecture team can review. Link will be provided. Architecture team to review by early January. Working draft: Need to decide where this lives for the upcoming release (GitBook, linked, PDF)?
| |
Deployment scripts for BBs in Sandbox | 10 minuteas | Where should these live? Both ID and Payments have created scripts in the BB repositories. Defining a standard structure (directories, names, etc) for deployment scrips for BBs going in to the sandbox | |
Technical Roles for 2024 | 10 minutes | Discussion on technical roles/functions needed within GovStack in 2024. Potential functions are:
| |
Prioritize future topics | 10 minutes |
|
Action Items
Ramkumar to connect with Hani/Nico on infra requirements
Additional Future Topics
SSO vs. central portal - can we provide guidance for both?
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?
Decoupling BBs into smaller pieces, as well as talking about an approach for existing products which span multiple BBs
How to articulate the different levels/scopes of building blocks - foundational/DPI, functional, and possibly application (things like eMarketplace). This should be clearly articulated in GovStack documentation. Also articulate how service blocks fit in to this paradigm.
Identify BBs that are missing/needed and develop plan to address those new BBs - get feedback from Egypt and Kenya meetings
Questions about IM from Egypt deep dive
Exchanging large amounts of data through IM (MRIs, etc)
Real-time streaming
Taylor: we'd likely need to find some experts on open-source video chat apps, see how https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-quickstart/ fits into the IM, and ALSO talk about things like email clients and servers
Defining user personas and journeys - outputs would be overall messaging, providing high-level guidance. How does GovStack work to deliver value.
Providing guidance on specific questions coming from country engagement
Example implementations - having BB groups work on them.