GET /api/issuer/useCaseParticipation - missing response body pending state #109
Comments
jjeroch
changed the title
Phil91
added a commit
that referenced
this issue
May 8, 2024
* adjust GET /api/issuer/useCaseParticipation to return pending credentials as well * adjust GET /api/issuer/certificates to return pending credentials as well Refs: #109
Phil91
added a commit
that referenced
this issue
May 8, 2024
* adjust GET /api/issuer/useCaseParticipation to return pending credentials as well * adjust GET /api/issuer/certificates to return pending credentials as well Refs: #109
9 tasks
Phil91
added a commit
that referenced
this issue
May 12, 2024
* adjust GET /api/issuer/useCaseParticipation to return pending credentials as well * adjust GET /api/issuer/certificates to return pending credentials as well Refs: #109 Reviewed-By: Norbert Truchsess <[email protected]>
This was referenced May 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Detected in Version 1.0.0 RC3
Scenario:
The credential holder (aka customer) requests a credential.
Example: Traceability v2
The request is successfully submitted.
Now calling the endpoint
GET /api/issuer/useCaseParticipationResponse Body:
{ "expiry": "2024-12-23T00:00:00+00:00", "id": "1268a76a-ca19-4dd8-b932-01f24071d563", "template": "https://catena-x.net/fileadmin/user_upload/04_Einfuehren_und_umsetzen/Governance_Framework/231016_Catena-X_Use_Case_Framework_Traceability.pdf", "validFrom": "2023-06-01T00:00:00+00:00", "verifiedCredentialExternalTypeId": "TRACEABILITY_CREDENTIAL", "version": "2.0", "ssiDetailData": null // ssiDetailData section is supposed to respond with the PENDING state }The
ssiDetailDatasection of the response is supposed to be in the PENDING state.The text was updated successfully, but these errors were encountered: