Weekly Sync - 02 July 2024

[github-actions[bot]]

Please add agenda items below and give your weekly update in a comment. Thank you!

Agenda

@sabineschaller Should we make Kratos optional?
@raducristianpopa RS error codes - just like we have for AS

Meeting Notes

Should we make Kratos optional?

-We've seen delays in upgrading to newer versions due to resistance against mandatory Kratos implementation for the Admin UI login.

• Considering making Kratos optional to encourage integrators to update to the latest Rafiki versions.
• The development work required to make auth optional for the Admin UI would not be too great.
• In scenarios where the Admin UI is operated internally and protected from external exposure, Kratos may not be necessary.
• There were questions about the cost of running Kratos if it remains largely unused.
• Another argument for keeping Kratos is its ability to create user groups which could potentially help in getting a Multi-Tenant configuration going for Rafiki. Multi-tenancy involves a single entity managing multiple ASEs and ensuring isolation of their instructions from each other.
• The conclusion is that we still need to gather more information about what exactly the pain points are for integrators.

RS error codes

• We upgraded Rafiki to have better GNAP error codes for the AS, the question is when we are gonna do this for the RS, since this is essential for web monetization work.
• This is on the agenda already. The outstanding decision is regarding whether or not we should include those error codes in the spec itself.
• These changes would need to take place in the Open Payments SDK rather than Rafiki itself.

[JoblersTune]

Working on adding additional telemetry metrics (tracking number of prepare, fulfill, and reject packets).