2026-03-03 - ACA-Py Users Group Community Meeting

2026-03-03 - ACA-Py Users Group Community Meeting

Summary:

  • Releases are out, Integration test issues, Credo-based Mediator, what’s next?

Call Time: 8:00 Pacific / 16:00 Central Europe

Zoom Link:

https://zoom-lfx.platform.linuxfoundation.org/meeting/96618113800?password=3fb31a65-606d-4765-8f89-ce7c857dc049

Call Recording:

https://zoom.us/rec/share/FVII3ZTSeclQF2ersLxKyoWPp3ddlCtFWPHiSJUcHLJq1Ktxo6lrjftMLUkLR0Bi.gz-SWdFUl3WaVFsj

image-20241112-180131.png
image-20241112-180041.png

Welcome, Introductions and Announcements

Announcements:

  • Stephen presented at the W3C Credentials Community Group (CCG) Meeting on Tuesday, Feb. 17 – Recording, Slides, Transcript.

Documentation:

Agenda

  • Release 1.5.1, 1.3.3 and 1.26 all out this past week. w00t!

  • What’s up with the automated tests?

    • Recent/Current issues:

      • 2 BBS Tests in the Interop Tests - disabled in a PR that has been merged.

        • But these tests are passing locally.

        • Seems to be with DIF Presentation Exchange

        • Approach is to leave for someone interested in getting BBS working. Issue 4073 for that.

      • 6 Failing tests in the Postgres Tests in a dependabot PR – likely the PR actually breaks the test. Yay!

        • Investigate the library that is being updated.

        • Decision – merge or not.

      • Redis Cluster Plugin integrated test failing as well – Patrick is working this.

    • Regards the “works locally” issue – how do we test using the GH Runners?:

      • Put in a “Manual Tests” workflow that we can update as needed to manually trigger isolated tests.

      • Make as easy as possible – e.g have a variable that we list the tags of the tests to run and then run the other workflows.

  • Transition to the Credo Mediator at BC Gov. – Jamie Hale

    • Why the change? Answer – align the mediator stack with the Wallet so same team could manage it.

      • Not because the ACA-Py version wouldn’t work or was flawed – both needed work, BC chose to do that work in the Credo version.

    • How it was done

      • Updates to Credo to add support needed for scaling both the message handling layer (including websockets from a single Wallet moving between pods) and pickup protocol updates.

      • Two databases – the Askar database with keys and connections, a message queue management.

        • Both done in Postgres, so fewer dependencies, but the latter could have been done in Redis.

          • Postgres queuing support greatly improved recently, so performance loss not big – and one less dependency.

      • Script to update in place the Askar database. No loss of connections that already existed.

      • Migration: Backup, shutdown ACA-Py Mediator, run update script, startup Credo Mediator.

        • If problems – stop Credo Mediator, restore from backup, startup ACA-Py Mediator

    • Could ACA-Py be improved to support same features

      • Definitely. Some guidance was provided. Same architecture could be used, improve pickup (although pickup behaviour was already improved from start of work). Remaining work is getting the scaling right – which was most of the work needed in the Credo Mediator as well.

  • Review of PRs, recently closed PRs and Issues:

  • What’s next? Ideas…

    • Some work has been done on removing Indy logic/dependencies from the core and into a plugin. This is probably the most important change to be made, as it would greatly simplify the ACA-Py core and the building of additional plugins.

  • Open Discussion

Important Links:

Discord: https://discord.com/invite/yjvGPd5FCU (Click Accept Invite, check out the #aca-py channel)