Skip to content

Out-of-band metadata not persisting after invitation accepted #3841

@EugeneContactable

Description

@EugeneContactable

Hi, I'm hoping I can get some clarity here as I'm not sure if this is a bug or if I'm missing something.

I'm currently building a solution as a custodial model, and I have a single AcaPy instance running in multitenancy mode. I'm using anoncreds as the credential format.

The scenario:

  • An "issuer" tenant needs to request proof from a holder tenant once an OOB invitation has been created and accepted and connections are active. I would like to use the metadata once the connection is active on the issuer tenant to create a proof request for the holder to present some credential. This is also used similarly for an issuance flow. The metadata is used to determine which attributes to request proofs for once the invite has been accepted by the holder.

The Flow:

  • I create an OOB Invite via the issuer tenant as the initiating entity, and I populate the metadata attribute on the OOB Invite payload.
  • Via the webhook when the invitation has been created and is in state "await_response" I can then query the connections/{conn_id}/metadata endpoint for the issuer tenant and see the metadata has persisted correctly.
  • However once the invitation is accepted via the holder tenant, the connection on the issuer tenant has lost the metadata, i.e once the OOB webhook state "done" is received, the connection on the issuer tenant no longer has the metadata (connections/{conn_id}/metadata returns an empty object).

This seems odd to me. I know a proof presentation can be included as an attachment on the OOB but I have yet to add one that works so maybe that is the answer although I am struggling with that path too. The Swagger simply says indicates the structure:
"attachments": [
{
"id": "attachment-0",
"type": "present-proof"
}
]
and I have yet to find clear documentation on how to achieve this attachment approach.

Any and all help would be greatly appreciated.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions