You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current implementation looks like the VP is verified in MIW and then the content is checked in EDC / an EDC extension.
One of those checks is (also according to the relevant standard CX0018) that the issuer of the VC is the (or to be more precise a) dataspace operator.
And exactly this small difference of the or a is relevant here. The current implementation seems to allow exactly 1 tx.ssi.miw.authority.id which looks like to me that there is only 1 issuer possible.
I think it is important, though, that multiple such issuers are possible. This is the case in a multi-OpCo environment.
I think there are 2 ways forward, a short term workaround and a long term solution.
short term:
Make tx.ssi.miw.authority.id a list instead of a single string.
Beware, that also the prefix is very likely different!
long term:
There should be a hosted list I guess which is signed by the CX association that contains valid (trusted) issuers of VCs.
It needs to be clarified whether a second OpCo is Release 3.2 relevant or not.
--
Matthias Binzer
The text was updated successfully, but these errors were encountered:
Current implementation looks like the VP is verified in MIW and then the content is checked in EDC / an EDC extension.
One of those checks is (also according to the relevant standard CX0018) that the
issuer
of the VC is the (or to be more precisea
) dataspace operator.And exactly this small difference of
the
ora
is relevant here. The current implementation seems to allow exactly 1tx.ssi.miw.authority.id
which looks like to me that there is only 1 issuer possible.I think it is important, though, that multiple such
issuers
are possible. This is the case in a multi-OpCo environment.I think there are 2 ways forward, a short term workaround and a long term solution.
short term:
Make
tx.ssi.miw.authority.id
a list instead of a single string.Beware, that also the prefix is very likely different!
long term:
There should be a hosted list I guess which is signed by the CX association that contains valid (trusted) issuers of VCs.
It needs to be clarified whether a second OpCo is Release 3.2 relevant or not.
--
Matthias Binzer
The text was updated successfully, but these errors were encountered: