Summary:
| Excerpt |
|---|
Topics:
|
...
Recordings From the Call:
| Widget Connector | ||
|---|---|---|
|
|
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
- IIW coming up April 16-18.
- Thread in Hyperledger Discord on IIW.
- Identity Working Group – this Thursday Jorge Flores on ecosystem building
Attendees
- Stephen Curran (BC Gov/Cloud Compass Computing Inc.) <swcurran@cloudcompass.ca>
- Emiliano Suñé (BC Gov/Quartech) <emiliano.sune@quartech.com>
- Wade Barnes (BC Gov / Neoteric Technologies Inc.) <wade@neoterictech.ca>
- Daniel Bluhm (Indicio PBC) <daniel@indicio.tech>
- Patrick St-Louis (DTLab-LabCN/Open Security and Identity inc.) <patrick.st-louis@opsecid.ca>
...
- Status Updates:
- AnonCreds RS in ACA-Py
- PRs for AnonCreds+CredX concurrently – after the 0.12.0 release
- Upgrade script – complete.
- did:peer and AFJ Interop
- Connection reuse for did:peer:2/4
- AnonCreds RS in ACA-Py
- Status of ACA-Py 0.12.0
- Additional PRs to go into the release? Yes – list:
- PR 2862
- Issue 2859
- Another update – missing verification method in VC-DI.
- Additional concepts? No
- Additional PRs to go into the release? Yes – list:
- Status of ACA-Py 1.0.0 Release:
- Checklist Issue, labelled Issues and PRs
- Other issues/PRs to be added?
- PR 2348 2860 - handling authorization to update base/tenant wallet.
- Should we wait on the AnonCreds RS work?
- LTS Considerations per Aries RFC 0799 Long Term Support
- Other considerations?
- Checklist Issue, labelled Issues and PRs
- Logging for Tenants - Akiff Manji is working on this.
- Trying to refactor it a bit – goal is to make it multi-tenant
- Any ideas on thoughts on making it easier/cleaner?
- First time – change every instance of logger being used – painful change.
- Should be able to configure it without changing every instance.
- Use the logging interface and inject something about the tenant.
- Should the multi-tenant be separated from the single-tenant logging?
- Should we switch to "mutli-tenancy" always – where the current non-multi-tenant is simply multi-tenant with just one tenant.
- Reduce complexity, reduce branches in code.
- Once Indy SDK support is dropped, it will be easier since Askar is inherently like that.
- Interesting differences in approaches, both of which are viable:
- Traction – independent controllers one per traction tenant.
- Single controller – that manages each of the tenants.
- DISCUSS: When to officially drop support for the Indy SDK?
- How to transition to did:indy?
- Vulnerability in the OpenSSH library disclosed last Friday
- Long time GitHub contributor tried to push a remote execution – in xz-utils - bleeding edge version, but caught before it got to the major distributions.
Upcoming Meeting Topics:
Future Topics
...