Uploaded image for project: 'EVSClient'
  1. EVSClient
  2. EVSCLT-733

[KELA] Detect signature in CDA documents and validate

    Details

    • Type: Story
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 5.4.0
    • Fix Version/s: 5.5.0
    • Component/s: CDA Validation
    • Labels:
      None

      Description

      General use case description
      1. User chooses to validate an XML object in EVSClient
      2. Schematron or model-based validation is performed to the object normally. Schematron rules may contain basic validation of the signature contents, such as checking whether correct digests have been used etc.
      3. EVSClient detects whether the file contains an XML signature by checking if the file contains a <ds:Signature> element. There may be multiple signatures in the same file. If no signature is located, the use case stops here. Namespace prefix “ds” stands for "http://www.w3.org/2000/09/xmldsig#".
      4. A link “Validate enveloped signature” is shown next to the object contents in the same way as a link to PDF validation is shown when the object contains an enveloped PDF.
      5. User clicks the signature validation link.
      6. Validation of signature(s) is performed and the result is shown to the user. Each signature is validated separately.
      7. Alternatively (a better option) the validation may be performed immediately in parallel with other validation (XSD schema and schematron or model-based validation) and results are shown together with other results on the same page.

        Attachments

          Activity

            People

            • Assignee:
              hra Hilary Rabe
              Reporter:
              aberge Anne-Gaelle Berge
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 2 days Original Estimate - 2 days
                2d
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 2 days, 4 hours, 45 minutes
                2d 4h 45m

                  Potential Duplicates