Skip to content
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

Open
wants to merge 64 commits into
base: develop
Choose a base branch
from

Conversation

sree96
Copy link
Contributor

@sree96 sree96 commented Nov 26, 2024

No description provided.

@sree96 sree96 force-pushed the injiver-587-ovp-endpoints branch 3 times, most recently from 7e1cbcb to db67f41 Compare November 27, 2024 04:40
@sree96 sree96 requested a review from swatigoel November 27, 2024 04:42
@sree96 sree96 force-pushed the injiver-587-ovp-endpoints branch from 5c3b25d to 32174f8 Compare November 27, 2024 10:00
@sree96 sree96 force-pushed the injiver-587-ovp-endpoints branch from 32174f8 to c8a582c Compare December 2, 2024 06:51
@sree96 sree96 requested a review from vishwa-vyom December 6, 2024 06:50
pom.xml Show resolved Hide resolved
verify-core/.mvn/wrapper/maven-wrapper.properties Outdated Show resolved Hide resolved
verify-core/pom.xml Outdated Show resolved Hide resolved
verify-core/pom.xml Outdated Show resolved Hide resolved
verify-core/pom.xml 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);
Copy link
Member

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 ?

Copy link
Contributor Author

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

Copy link
Member

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 ?

Copy link
Contributor Author

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.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

??

@vishwa-vyom
Copy link
Member

Also unit test case files were missing this PR

@sree96 sree96 force-pushed the injiver-587-ovp-endpoints branch from 5a7bbc6 to 663470a Compare December 11, 2024 11:52
@NoArgsConstructor
@AllArgsConstructor
public class StatusDto {
SubmissionState status;
Copy link
Member

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.

Copy link
Contributor Author

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.

Copy link
Member

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.

Copy link
Member

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

@Autowired
GsonSingleton gsonSingleton;

@GetMapping(path = "/vp-result/{transactionId}")
Copy link
Member

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.

Copy link
Member

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

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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants