search

eclipse-tractusx / sig-release

https://eclipse-tractusx.github.io/sig-release
Apache License 2.0
8 stars 8 forks source link

Fix incompatibility/deprecation issue between issuance, wallet and EDC #832

Open lgblaumeiser opened 2 months ago

lgblaumeiser commented 2 months ago

Description

Details to be found here: https://github.com/eclipse-tractusx/ssi-credential-issuer/issues/224 Finding 3

Issue in EDC is here: https://github.com/eclipse-edc/Connector/issues/4357

Basic issue is that there are different formats for the revocation list:

EDC implements only StatusList2021 as of now MIW is planned to support BitStringStatusList Intention is to get rid of the deprecated format.

Impact

The planned procedure is to support BitStringStatusList in all relevant components first but stick in the operation to StatusList2021. Have a clear communication on when BitStringStatusList will be used. This will render older EDC versions to be not compliant with the mechanism anymore. So switching to BitStringStatusList is a breaking network change that must be coordinated.

Goal is to do the change prior to 2026 which would violate the 1 + 1 Release Schedule.

Additional information

lgblaumeiser commented 2 months ago

@jjeroch : Does this summarize the issue we discussed this morning, can you add missing details or forward the issue to people who can?

@stephanbcbauer : This is a feature that we should add to the 24/12 release and coordinate between the teams. It is about ensuring that all relevant components support BitStringStatusList and StatusList2021 for now. This enables us to switch at any time convenient in the future.

stephanbcbauer commented 1 month ago

I added the milestone 24.12, because we need it on the board. Let's discuss this feature tomorrow in our meeting

Phil91 commented 1 month ago

I've added a ticket for the portal team to support the BitString Status List: see #404

paullatzelsperger commented 1 month ago

Just as a small and admittedly detailed comment from the EDC side: yes, we will support BitStringStatusList in future versions (tx-edc probably 0.8.x), but so far we have limited it to support only statusSize = 1, i.e the only valid states are "set" and "not-set".

This is permitted by the spec and still satisfies conformance.

There are also two other implementation issues on which all involved parties should have alignment: