Skip to content

Commit

Permalink
Fix for insertion breaking use case (#516)
Browse files Browse the repository at this point in the history
  • Loading branch information
Sahil-tarento authored Mar 22, 2024
1 parent 5141801 commit 0406353
Showing 1 changed file with 2 additions and 2 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -136,7 +136,7 @@ public PullURIResponse generateURIResponse(String digiLockerHmac, String request
userEnrollment = userEnrollment.stream().filter(enroll -> ((String) enroll.get("token")).equalsIgnoreCase(certificateAccessCode)).collect(Collectors.toList());
dockerLookUpInfo.put(Constants.CERTIFICATE_ID, userEnrollment.get(0).get(Constants.IDENTIFIER));
try {
dockerLookUpInfo.put(Constants.LAST_ISSUED_ON, simpleDateFormat.format(dateFormat.parse((String) userEnrollment.get(0).get(Constants.LAST_ISSUED_ON))));
dockerLookUpInfo.put(Constants.LAST_ISSUED_ON, dateFormat.parse((String) userEnrollment.get(0).get(Constants.LAST_ISSUED_ON)));
} catch (ParseException e) {
responseStatus.setStatus("0");
logger.error("Not able to parse date");
Expand All @@ -153,7 +153,7 @@ public PullURIResponse generateURIResponse(String digiLockerHmac, String request
certificateAddInfoDTO.setDocumentInfo(request.getDocDetails().getDocType());
certificateAddInfoDTO.setCertificateName((String)dockerLookUpInfo.get(Constants.CERTIFICATE_NAME));
certificateAddInfoDTO.setDocumentName(DocumentType.getValueForKey(request.getDocDetails().getDocType()));
certificateAddInfoDTO.setCertificateIssueOn((String)dockerLookUpInfo.get(Constants.LAST_ISSUED_ON));
certificateAddInfoDTO.setCertificateIssueOn(simpleDateFormat.format((Date)dockerLookUpInfo.get(Constants.LAST_ISSUED_ON)));
certificateAddInfoDTO.setUserName((String)getUserInfo.get(Constants.FIRSTNAME));
certificateAddInfoDTO.setSwd((String)getUserInfo.get(Constants.CHANNEL));
certificateAddInfoDTO.setSwdIndicator(String.valueOf(((String)getUserInfo.get(Constants.CHANNEL)).charAt(0)));
Expand Down

0 comments on commit 0406353

Please sign in to comment.