Hi, I’m working on Problem Statement #2 – Inji Interoperability Playground.
I’ve gone through the problem statement and understand that the playground should test interoperability across the Issuer → Wallet/Holder → Verifier flow, support multiple credential formats, expose protocol exchanges, and report interoperability results.
My remaining doubt is about the test matrix.
Should we define specific combinations of existing Inji components/configurations/formats and test them against each other, or is the expectation mainly to demonstrate the interoperability scenarios described in the problem statement?
In other words, how should we determine which combinations/scenarios are expected to be tested, rather than trying to test every possible combination?
An example of the expected test scenario structure would help us design the playground correctly.
Yes, the expectation is to build a configurable interoperability playground that reflects the Inji ecosystem, while also allowing us to demonstrate interoperability with other credential stacks.
A few things we should consider while designing the playground:
1. Issuer Section
The Issuer section should represent the credential issuance side of the Inji ecosystem.
We should support the different credential types that can be issued through Inji Certify. You can refer to the list of supported credentials in Inji Web on the Collab environment: INJI Wallet
The UI should allow the user to select:
Issuer
Credential type
Relevant issuance configuration
Once the issuer and credential type are selected, the user should be able to choose the issuance flow, for example:
Authorization Code
Pre-Authorization Code
Based on the selections, the Issuer section should generate the relevant credential offer / QR code.
The QR code should be scannable by Inji Mobile Wallet or another compatible wallet.
The architecture should ideally allow additional issuers to be added later rather than being limited to Inji Certify.
2. Wallet Section
The Wallet section should represent the holder side.
We should provide references/options for:
Inji Mobile Wallet – Android
Inji Mobile Wallet – iOS
Inji Web Wallet
For the mobile wallets, you can refer to the available information in the Collab environment:
For the Web Wallet:
The objective at this stage is not necessarily to implement another wallet inside the playground, but to allow the playground to clearly represent which wallet is being used in a given interoperability scenario and provide the appropriate way to continue the flow.
3. Verify Section
The Verify section should represent the verifier side using Inji Verify.
Support the VP verification flow through Inji Verify.
Based on the selected configuration, the Verify section should generate the appropriate presentation request / QR code for the wallet to scan.
4. Interoperability
The above gives us the Inji ecosystem baseline:
Inji Certify → Inji Wallet → Inji Verify
But the key purpose of this playground is to demonstrate interoperability beyond the Inji ecosystem.
For example:
External Issuer → Inji Wallet → Inji Verify
One example could be using an external credential stack such as the Animo playground:
We could obtain a credential from the external issuer and then attempt to present that credential to Inji Verify.
Similarly, we should be able to explore scenarios such as:
Inji Certify → External Wallet → Inji Verify
External Issuer → Inji Wallet → Inji Verify
External Issuer → External Wallet → Inji Verify
Inji Certify → Inji Wallet → External Verifier, where relevant
The objective is not to test every possible combination. We should define a curated set of representative scenarios that demonstrate interoperability across the important dimensions.
5. Credential Formats and Protocols
The playground should allow us to demonstrate interoperability across the relevant supported:
Credential formats
OpenID4VCI flows
OpenID4VP flows
Issuers
Wallets
Verifiers
For example, a scenario could be:
External Issuer → Inji Mobile Wallet → Inji Verify
with:
Credential format: SD-JWT VC
Issuance: OpenID4VCI
Presentation: OpenID4VP
Another scenario could use a different credential format or an external wallet.
Again, we don’t need to create a Cartesian-product matrix of every issuer × wallet × verifier × credential format. The focus should be on meaningful representative interoperability scenarios.
6. Protocol Exchange / Test Result
An important part of the playground should be making the interoperability process visible rather than only showing a final Pass/Fail.
For example, for an issuance flow we should ideally be able to see:
The important distinction is that we want to take this one step further for Inji by making the interoperability scenarios, protocol exchanges, and test results explicit.
This should give you enough direction to start designing the overall playground and the initial test matrix.