Clarification on Interoperability Test Scenarios for Inji Interoperability Playground

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.

Hi Yashaswini_K_P

Thank you for reaching out to us. We will check the issue and get back to you shortly.

Regards,
Mrudula
on behalf of Team MOSIP

Hi @Yashaswini_K_P,

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.

  • You can refer to:
    Inji Verify

  • The UI should allow the user to select/configure the credentials that need to be requested.

  • The currently supported credentials can be identified through the Request Verifiable Credentials flow in Inji Verify.

  • We should provide a way for the user to customise the Verifiable Presentation request.

  • The existing Inji Verify configuration can be used as a reference:
    inji-verify/helm/inji-verify-ui/files/config.json at v1.0.0-alpha.1 · inji/inji-verify · GitHub

  • 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:

Credential Offer → Authorization → Token Request/Response → Credential Request/Response → Credential Issued

And for presentation:

Presentation Request → Credential Selection → Presentation → Verification

The playground should ideally report:

  • Which components were involved

  • Credential format

  • Protocol/version

  • Individual exchange/steps

  • Success/failure at each stage

  • Overall interoperability result

  • Where the interoperability failure occurred, if any

This will make it useful as an actual interoperability test environment, rather than just a collection of demos.

7. Extensibility

The architecture should allow us to add new:

  • Issuers

  • Wallets

  • Verifiers

  • Credential formats

  • Protocols

  • Test scenarios

without having to redesign the core playground each time.

For the initial implementation, I would suggest starting with a few representative scenarios covering:

Inji ↔ Inji
Inji ↔ External
External ↔ Inji

and then expanding the scenarios as we onboard more external credential stacks.

References

You can also refer to these playgrounds to get an idea of how this type of experience can be structured:

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.

Best regards,
On behalf of Inji