feat: add DCP issuance #517
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
paullatzelsperger
force-pushed
the
feat/dcp_issuance
branch
2 times, most recently
from
daeb840 to
1b775d6
Compare
Contributor
Author
paullatzelsperger
force-pushed
the
feat/dcp_issuance
branch
2 times, most recently
from
0b0a790 to
cb8d42d
Compare
paullatzelsperger
force-pushed
the
feat/dcp_issuance
branch
from
d6da2b0 to
0d07b22
Compare
Contributor
Author
|
@rafaelmag110 @lgblaumeiser this PR will land DCP issuance in MXD, and it also adds an E2E test to verify that. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
this PR introduces DCP issuance, with which dataspace participants can request additional credentials from the Dataspace Issuer Service.
It also adds another component called a Dataspace Issuer Service to create and deliver VerifiableCredentials.
Important
NB: in its current form, the Dataspace Issuer is not yet used to issue MembershipCredentials and DataExchangeGovernance credentials, only `NameCredentials. These are still being created statically and created using the IdentityAPI. Subsequent Pull-Requests will add that functionality at a later point.
Because there isn't an official release of
Tractus-X IssuanceServiceandTractus-X IdentityHubHelm charts yet, those components are still deployed using raw Kubernetes deployments rather than Helm releases.Pre-review checks
Please ensure to do as many of the following checks as possible, before asking for committer review: