Versions Compared

Old Version 1

changes.mady.by.user Stephen Curran

Saved on

compared with

New Version Current

changes.mady.by.user Stephen Curran

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Recordings From the Call:   20230221 ACA-Py User Group Community Meeting Call Recording.mp4

  • Full Meeting:  
  • Topics:

Hyperledger is committed to creating a safe and welcoming

community for all. For more information

please visit the Hyperledger Code of Conduct.

Welcome, Introductions and Announcements

  • AnonCreds v2.0 Working Group – Meetings
  • OWF Presentation on Aries

Attendees

Agenda

  • Update on BC Gov Code With Us – ACA-Py Indy-SDK to Askar conversion script - Indicio
    • Update on ACA-Py Container Scanning (brought up last meeting)
      • There are scanner options in Hyperledger, but not chosen.
        • Snyk is a possibility, Qualys was also used and both produced the same results.
      • Based on the testing, the base images were updated to bullseye, which contains no current critical vulnerability.
      • Would like to have multi-architecture release.
    • Plugins discussion – Ian Costanzo
      • https://docs.google.com/presentation/d/1DoBsDGUEGtodteX57-O8S0TD22XrQFwL8unsals-MaY/edit?usp=sharing
      • Recommended: An "app store" repo of community developed, accepted ACA-Py Plugins, plus a directory of all ACA-Py Plugins, within or outside of the community plugins repo
      • Suggestions given on the last page of potential plugins pulled from the core – mediator, endorser considered to be high on the list, also, DID Methods, VC formats and AnonCreds methods.
      • The Event Bus is a useful component for triggering activation of plugins, but care must be taken to not use it for cross-instance communication. Rely on queuing for that.
      • Extend AATH to support the use of plugins for tests.
      • Potential issue – plugins dependent on plugins could create the need for a package manager-type functionality.
        • For now, developers must manage plugins by updating both the Python requirements and the plugins references in the config params/YAML.
    • Didn't get to these issues – run through these next meeting.
      • Updates from previous meetings:
        • Update on ACA-Py Container Scanning (brought up last meeting)
        • Multi-architecture containers
          • Issue with BBS+ package – doesn't support ARM containers – need an update to their CI
          • Solution: A third container published that includes BBS+ package, but is single architecture
          • Others are Askar and Indy-SDK
        • Messages getting stuck when a connection is being established
      Messages getting stuck when a connection is being established.
      • Message sent to the mediator, received, but connection not setup and message getting stuck.
      • Race condition.
      • Workaround in Bifold, but fix should be in the mediators – hence in ACA-Py/AFJ mediators.
      • On making a connection, the mediator routing and the connection are done in parallel, vs. serial.
      • Issues in ACA-Py and AFJ submitted – each need to be investigated
      • PR: 2079 – tricky part is the multiple version support.
      • Proposed approach:
        • Use docusaurus
        • Static site generated from new repo – https://github.com/hyperledger/aries-acapy-docs
        • Landing page in new repo, version specific documentation in folders.
        • GHA manually added for each supported ACA-Py release – automate this in future via a PR created with ACA-Py tag released.
          • Fetch tagged branch from ACA-Py into temp folder
          • Generate a root document if not present (used to support tags created in the past) – else, use one in ACA-Py.
          • Generate the required RST documents for the ACA-Py internal documentation currently used by Read The Docs (using Python doc strings).
          • (Re-)Generate static pages for the tag into correct folder in the docs repo.
        • For now, periodically run the GHA for the "main" branch manually – automate this in the future to run either nightly or when an ACA-Py PR is merged.
        • Publish to "acapy.org" domain.
    • Next Release?
      • 0.7.6 or 0.8.0 (depending on breaking changes)
      • Not a cherry-picked release – everything in main branch
      • Issues include fixing/adding revocation notification issues
    • Issue 2029: Additional security controls for webhooks for multi-tenancy
      • Added as a PR and then closed, to be refactored as a plugin
      • Enables key updates via an admin interface call.
    • Open Discussion:
      •  
      • Does anyone use/see a use case for Web Sockets and Return Route beyond ACA-Py as a mobile agent mediator?

    ...

        • Next Release – completed – 0.8.0-rc0
          • Ready for final 0.8.0 release?
          • Ready for a 1.0.0-rc2 release? 
    • Important updates to be made to ACA-Py
      • Presentation: ACA-Py Focus on Adoption
        • DID Handling – all DIDs
          • And AnonCreds objects on any ledger/VDR
        • AIP 2.0 completion, including AATH tests
        • Cleanup tasks
        • Multi-tenant: Instance features made adjustable by tenants
        • Refactoring – especially with plugins
        • OCA Support
        • Building on the AFJ OpenID4VCs capabilities – what they are, how to use them.
    • Open Discussion

    Upcoming Meeting Topics:

    • Does anyone use/see a use case for Web Sockets and Return Route beyond ACA-Py as a mobile agent mediator?
    • Understanding Presentation Request Revocation Intervals
    • Status of vc-authn-oidc repository – v2.0 branch.

    ...