Summary:
Planned Topics:
- Getting to release 0.7.4 – key release notes and breaking changes?
- Persistent Queues update – design change to make PQs an external plugin
- Multi-tenancy security and questions raised in issue 1632: --multitenant-admin security questions
- Endorser for multi-tenant agents
- Including seed in the Admin Interface
Recording from the call: To Be Added
|
Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit the Hyperledger Code of Conduct. |
|---|
Welcome and Introductions
Attendees
- Stephen Curran (Cloud Compass Computing Inc.) <swcurran@cloudcompass.ca>
Announcements
Deployments and Work Updates
- BC Gov Team
- Aries Cloud Agent Python
- Aries Shared Components – indy-vdr, indy-shared-rs and aries-askar
- Aries-VCR/OrgBook BC Deployment
- Issuer Kit - VCs for OIDC Issuer Service
- Aries Agent Test Harness work - Results page: https://aries-interop.info
- Aries Mobile Test Harness
- BPA - Business Partner Agent for B2B use of VCs
- BC Wallet – based on Aries Framework JavaScript and Aries Bifold
Agenda
- Update on Release 0.7.4
- PRs since Release 0.7.3 - Open PRs
- Update: Adding persistent queues in ACA-Py – Shaanjot Gill
- Multi-tenancy security and questions raised in issue 1632: --multitenant-admin security questions
- Endorser for multi-tenant agents – issue 1657
- Including the seed as a parameter in the Admin interface – issue 1640
- To merge or not to merge, that is the question: 1620 - Updates to Connection State
- Summary from Philipp.Etschel: I think this task started as a fix for a minor inconsistency between documentation, connection record and connection event and then mutated into a whole discussion about the deprecation of the connection protocol. So I would propose to either just fix the inconsistency, or wait until there is a decision on how to proceed. Basically there are three open questions.
- 1. how to handle the connection states
- 2. how to handle the deprecation
- 3. how to migrate stored data.
- Summary from Philipp.Etschel: I think this task started as a fix for a minor inconsistency between documentation, connection record and connection event and then mutated into a whole discussion about the deprecation of the connection protocol. So I would propose to either just fix the inconsistency, or wait until there is a decision on how to proceed. Basically there are three open questions.