Scenario:
The credential holder (aka customer) requests a credential.
Example: Traceability v2
The request is successfully submitted and in State "PENDING".
Expected behavior
A second request of the credential can not get triggered as long as the current request is in state "PENDING"
Actual behavior
Another request can get triggered and gets stored in the DB
The issue is not major - since the double credential request will run into a double credential creation and storage. It is not an issue, but also not a benefit for the requester.
Decision: provide the response "already existing" if the user requests an already in status "PENDING" credential
Detected in Version 1.0.0 RC3
Scenario: The credential holder (aka customer) requests a credential. Example: Traceability v2 The request is successfully submitted and in State "PENDING".
Expected behavior A second request of the credential can not get triggered as long as the current request is in state "PENDING"
Actual behavior Another request can get triggered and gets stored in the DB
The issue is not major - since the double credential request will run into a double credential creation and storage. It is not an issue, but also not a benefit for the requester.
Decision: provide the response "already existing" if the user requests an already in status "PENDING" credential