Certify request: exception occurred

[smuellerDD]

I sent the following data to the /certify endpoint:

[
  {
    "esvVersion":"1.0"
  },
  {
    "itar":false,
    "limitEntropyAssessmentToSingleModule":false,
    "moduleId":12827,
    "vendorId":11176,
    "supportingDocumentation":[
      {
        "sdId":270031,
        "accessToken":"access token received for SD"
      }
    ],
    "entropyAssessments":[
      {
        "eaId":20154,
        "oeId":31916,
        "accessToken":"token obtained for ea"
      }
    ]
  }
]

The server returned:

[
  {
    "esvVersion": "1.0"
  },
  {
    "status": "error",
    "errors": {
      "errorList": [
        "TestPredicates: vendorId An Exception occured.",
        "TestPredicates: moduleId An Exception occured."
      ],
      "entropyAssessmentsReferences": {
        "elementList": [
          {
            "location": "indexPosition:1",
            "messageList": [
              "TestPredicates: oeId An Exception occured.",
              "TestPredicates: oeId An Exception occured."
            ]
          }
        ]
      }
    },
    "information": {
      "messageList": [
        "TestPredicates: vendorId An Exception occured.",
        "TestPredicates: moduleId An Exception occured."
      ],
      "entropyAssessmentsReferences": {
        "elementList": [
          {
            "location": "indexPosition:1",
            "messageList": [
              "TestPredicates: oeId An Exception occured."
            ]
          }
        ]
      }
    }
  }
]

Note: may I ask for a clarification on the relationship of the access token that should be used for the authorization bearer? At the moment, I use the ea-access token as authorization bearer.

[celic]

You can use any valid access token for the header. I am seeing this same error now, we are diagnosing the problem.

[smuellerDD]

Confirmed, working.

But what is the next step? I would have expected that I get a kind of request ID like for ACVP where I can ask NIST to give me a certificate?

[celic]

Next step is on the NIST side. Data gets bundled and sent to Resolve for a manual review. Labs are updated on progress using encrypted email via the normal module review process.

On Fri, Sep 10, 2021, 4:30 AM smuellerDD @.***> wrote:

Confirmed, working.

But what is the next step? I would have expected that I get a kind of request ID like for ACVP where I can ask NIST to give me a certificate?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/usnistgov/ESV-Server/issues/11#issuecomment-916730401, or unsubscribe https://github.com/notifications/unsubscribe-auth/AATQXELDHK3KJRFCDR7C3TDUBG63TANCNFSM44YEW7QA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[smuellerDD]

Am Freitag, dem 10.09.2021 um 05:41 -0700 schrieb Chris Celi:

Next step is on the NIST side. Data gets bundled and sent to Resolve for a manual review. Labs are updated on progress using encrypted email via the normal module review process.

Ok, but isn't there a kind of ID that allows us to refer to the open request? What happens if a lab has 10 parallel requests outstanding. How can we identify a particular outstanding validation?

Thanks Stephan

[celic]

Soon we will add in a TID (or similar) for a lab to track the entry.

On Fri, Sep 10, 2021, 9:06 AM smuellerDD @.***> wrote:

Am Freitag, dem 10.09.2021 um 05:41 -0700 schrieb Chris Celi:

Next step is on the NIST side. Data gets bundled and sent to Resolve for a manual review. Labs are updated on progress using encrypted email via the normal module review process.

Ok, but isn't there a kind of ID that allows us to refer to the open request? What happens if a lab has 10 parallel requests outstanding. How can we identify a particular outstanding validation?

Thanks Stephan

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/usnistgov/ESV-Server/issues/11#issuecomment-916889963, or unsubscribe https://github.com/notifications/unsubscribe-auth/AATQXELITTDIQCZJ7T2BDQLUBH7GLANCNFSM44YEW7QA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[celic]

Fixed in the latest release to Demo. Added an "EID" field for tracking a submission through the review process. Will update documentation.