Skip to content

Handle both legacy and current @type values in forward messages #119

@mirgee

Description

@mirgee

Currently, agency expects and uses legacy @type attribute for forward messages:

did:sov:BzCbsNYhMrjHiqZDTUASHg;spec/routing/1.0/forward

However, as per aries spec (see here), a different value should be used for the attribute:

https://didcomm.org/routing/1.0/forward

Agency should support both formats for some time in order to remain backwards compatible.

Analogous change was already implemented in aries-vcx (see here).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions