-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[INJIVER-587] - OVP Backend #239
base: develop
Are you sure you want to change the base?
Conversation
7e1cbcb
to
db67f41
Compare
5c3b25d
to
32174f8
Compare
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
32174f8
to
c8a582c
Compare
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
...c/main/java/io/mosip/verifyservice/services/VerifiablePresentationSubmissionServiceImpl.java
Outdated
Show resolved
Hide resolved
...c/main/java/io/mosip/verifyservice/services/VerifiablePresentationSubmissionServiceImpl.java
Outdated
Show resolved
Hide resolved
...c/main/java/io/mosip/verifyservice/services/VerifiablePresentationSubmissionServiceImpl.java
Outdated
Show resolved
Hide resolved
public AuthorizationRequestCreateResponseDto createAuthorizationRequest(AuthorizationRequestCreateDto vpRequestCreate) { | ||
|
||
String transactionId = vpRequestCreate.getTransactionId()!=null ? vpRequestCreate.getTransactionId() : Utils.createID(Constants.TRANSACTION_ID_PREFIX); | ||
String requestId = Utils.createID(Constants.REQUEST_ID_PREFIX); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the same transaction, if vp-request endpoint is called multiple times, we don't restricts ? How will you know which request id submission should be considered ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
submission is based on req-id which is unique and there can be only one submission at a time
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the questions is what happens when the create authorization request is called multiple times ?
Will it create a new request id, when the old request id is still valid ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Each time it will create a new req_id.
All the req_id is still valid because it represents a new transaction every time.
Its the verify FE tries to submit for latest req_id.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
??
...c/main/java/io/mosip/verifyservice/services/VerifiablePresentationSubmissionServiceImpl.java
Outdated
Show resolved
Hide resolved
Signed-off-by: Sreenadh S <[email protected]>
Also unit test case files were missing this PR |
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
5a7bbc6
to
663470a
Compare
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
@NoArgsConstructor | ||
@AllArgsConstructor | ||
public class StatusDto { | ||
SubmissionState status; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/{requestId}/status - SubmissionState status; - is little confusing since the request is expecting a request status and the status dto has a enum called SubmissionState and the field name is status.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lets just send the status alone as a response then. That makes more sense right.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As discusssed, lets have separate enums from VPRequestStatus and VPResultStatus and lets construct a proper json response only with status field when responding from vp request status API.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we discussed about removing COMPLETED and change to something like VP_SUBMITTED / VP_RECEIVED
...rc/main/java/io/mosip/verifycore/dto/authorizationRequest/AuthorizationRequestCreateDto.java
Outdated
Show resolved
Hide resolved
@Autowired | ||
GsonSingleton gsonSingleton; | ||
|
||
@GetMapping(path = "/vp-result/{transactionId}") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does is this fit inside this controller ?
As per the API categorization it was under VP request management, we should revisit this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we discussed to keep the result part as different controller right ? because of the exposure to internet vs protected endpoint
...e/src/main/java/io/inji/verify/dto/authorizationRequest/AuthorizationRequestResponseDto.java
Outdated
Show resolved
Hide resolved
verify-service/src/main/java/io/mosip/verifyservice/controller/VpSubmissionController.java
Outdated
Show resolved
Hide resolved
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
Signed-off-by: Sreenadh S <[email protected]>
No description provided.