2021-05-12 Aries Cloud Agent - Python Users Group Community Meeting
Summary:
Planned Topics:
- Queue Handling In ACA-Py
- When do we release the next ACA-Py?
- What's in AIP 2.0 that we need to add to ACA-Py
Recording from the call: dummyfile.txt
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
- Name (Organization) <email>
- Stephen Curran Stephen Curran (Cloud Compass Computing Inc.) <swcurran@cloudcompass.ca>
- Ajay Jadhav (AyanWorks) <ajay@ayanworks.com>
- Timo Glastra (Animo Solutions) <timo@animo.id>
Announcements
- ACA-Py Updates since 0.6.0:
- W3C Standard VCs/BBS+ CWU been merged
- DIF Presentation Exchange is ready to be merged
Deployments and Work Updates
- BC Gov Team
- Aries-VCR/OrgBook BC Deployment
- In progress: a multi-tenant OrgBook Issuer
- Issuer Kit - VCs for OIDC Issuer Service - Safe Entry BC PoC - VCs for Physical Access Points
- Vaccination/Test Result Verifiable Credential Issuer Service
- Aries Agent Test Harness work - Results page: https://aries-interop.info
- DID Exchange Test Cases; deprecating 0160 Connections usage
- Backchannel for Aries Framework Go
- BBS+ support to achieve W3C Standard VCs with ZKP and Selective Disclosure
- Including Presentation Exchange
- BPA - Business Partner Agent for B2B use of VCs
- did:indy, AIP 2.0
- Aries-VCR/OrgBook BC Deployment
Agenda
- Queues – Daniel Bluhm
- Persistent Queues work
- Needs more – something to add to queue, dequeue
- Actions:
- Daniel Bluhmto do a hackmd doc design to meet mediator-centric requirements, ideally with a narrative on push notification handling
- Andrew Whiteheadto do a hackmd doc design to meet scalabilty requirements
- Ideally, incorporated into the above, but if not, a third design doc, covering the use of the event bus with the outbound queuing
- Possible meeting ahead of next ACA-Pug meeting.
- When is the next ACA-Py release?
- Drivers: request for the resolver capability from BPA team, endorser signing functionality
- Pending merges:
- Any issues people want resolved?
- What up with canonicalized schema attributes – seems wrong.
- Demo Updates
- Documentation updates
- After those – are we ready? Other items to add?
- To Do:
- SICPA: Tweaks to resolver and docs.
- DIF Presentation Exchange merge when reviewed and ready.
- Andrew: 0.7.0-RC1 tag than 0.7.0 tag, optionally branch from there for 0.7.1 if needed (ideally, just tag 0.7.1 on main branch)
- Work to be done – needed sooner than later:
- Design/Support for Multi-key DID handling
- DID Registration API vs. DID Method specific API (e.g. the current did:web PR that has been proposed)
Next Meeting
- AIP 2.0 – what's got to be added to ACA-Py?
--aip20
flag to enable "breaking changes" features/completed community updates- RFC 0557 Discover Features V2 – Added AIP 2.0 features / potentially dynamic based on loaded modules
- RFC 0519 Goal Codes in specific protocols (RFC 0453/0454 - Credential Exchange V2), OOB
- Generalized support?
- RFC 0627 Static Peer DID Support
- RFC 0183 Revocation Notification – flag on API to notify user (+ connection_id?)
- RFC 0587 Encryption Envelope V2
- Review and update as needed all AIP 1.0 RFCs – to be added: a diff link for each "updated" RFC
Future Topics
- Double Signature with eIDAS?
- Background: https://www.slideshare.net/FIDOAlliance/introduction-to-fido-and-eidas-services
- SICPA - For the eSSIF program, with json-ld credential we are adding double signature, the normal + eIDAS
- Double signature in ACA-Py with pluggable mechanism, and implementation for eIDAS