ESV: Next step after data uploading?

[smuellerDD]

After finally getting all data uploaded (raw, restart, documentation), I get a verdict of success from the server. Yet, after sending the documentation, I also get a new access token.

What shall happen now?

[celic]

Documentation needs an access token because we've broken out the Certify process from the Entropy Assessment (Test Session). Certify is a separate end-point that accepts the eaIds, sdIds, and tokens for each to prove ownership.

[smuellerDD]

Am Dienstag, dem 09.03.2021 um 09:27 -0800 schrieb Chris Celi:

Documentation needs an access token because we've broken out the Certify process from the Entropy Assessment (Test Session). Certify is a separate end- point that accepts the eaIds, sdIds, and tokens for each to prove ownership.

Ok, but how can I proceed? I received the following data:

[
  {
    "esvVersion": "1.0"
  },
  {
    "uploadType": "UploadSupportingDocumentation",
    "status": "success",
    "dataLengthBytes": 773452,
    "accessToken":

What leads me to the next step? I.e. which URI do I have to access?

Thanks Stephan

[celic]

That's it. The documentation was uploaded and is waiting to be used in a certify when you are ready.

If you have suggestions to make this process clearer in the documentation, let me know.

On Tue, Mar 9, 2021, 2:36 PM smuellerDD notifications@github.com wrote:

Am Dienstag, dem 09.03.2021 um 09:27 -0800 schrieb Chris Celi:

Documentation needs an access token because we've broken out the Certify process from the Entropy Assessment (Test Session). Certify is a separate end- point that accepts the eaIds, sdIds, and tokens for each to prove ownership.

Ok, but how can I proceed? I received the following data:

[
{
"esvVersion": "1.0"
},
{
"uploadType": "UploadSupportingDocumentation",
"status": "success",
"dataLengthBytes": 773452,
"accessToken":

What leads me to the next step? I.e. which URI do I have to access?

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/9#issuecomment-794353163, or unsubscribe https://github.com/notifications/unsubscribe-auth/AATQXELCVWOZ3BIZV47WVN3TCZ2D7ANCNFSM4Y3ZBAVA .

[smuellerDD]

Am 09.03.2021 um 20:39 schrieb Chris Celi notifications@github.com:

 That's it. The documentation was uploaded and is waiting to be used in a certify when you are ready.

Maybe I miss a point here: what is the „certify“ operation? A PUT ?

Thanks Stephan

[celic]

Ah. Yeah the documentation doesn't have it yet because that endpoint is still in progress. The Certify will be a separate POST on a new endpoint. This is different than ACVP does it, and allows us to include multiple EAs in one request.

[smuellerDD]

Am 09.03.2021 um 20:58 schrieb Chris Celi notifications@github.com:

 Ah. Yeah the documentation doesn't have it yet because that endpoint is still in progress. The Certify will be a separate POST on a new endpoint. This is different than ACVP does it, and allows us to include multiple EAs in one request.

Ok, then I will wait until you are ready.

But what about providing the URI in the answer from the server just like the URLs provided in various ACVP responses?

Ciao Stephan

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[celic]

You mean the URI to the document that was just uploaded? We didn't intend for them to be retrievable by users. We should return the ID though (which was all the information the URIs were meant to provide). This is coming soon.

[smuellerDD]

You mean the URI to the document that was just uploaded? We didn't intend for them to be retrievable by users. We should return the ID though (which was all the information the URIs were meant to provide). This is coming soon.

I am referring to the URI for the next step, the certify operation. But that is only an idea without knowing how that certify is supposed to work.

Ciao Stephan

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[celic]

Yes you'll need the ID (which would be in the URI) for the Certify. Sorry, I was a bit confused. This is already done in our development branch of the Certify step, so I was getting a bit mixed up on what is on Demo versus our internal environment here.