Test communication between validator and MinIO in the stack

[EttoreM]

We need to make sure that the validator can read content from MinIO and use it to validate RO-Crates through the corresponding POST API endpoint.

[EttoreM]

@douglowe @elichad @alexhambley @AnnieZQH

I tested the integration between the validator and MinIO using the validator API POST endpoint that validates an RO-Crate stored in MinIO.

The steps carried out were as follows:

• First, I logged into MinIO using the credentials defined in .env rather than via Keycloak.

• Next, I created a new user with read and write permissions, since the existing user did not have permission to create a bucket or upload files.

• I then logged out and signed back in as the newly created user.

• After that, I created a bucket named ro-crates and uploaded the crate file workflow-1728-1.crate_validation.zip to it.

• I then used the validator API POST endpoint to validate the uploaded crate. The corresponding curl command was:

  curl -X 'POST' \
    'http://localhost:5001/v1/ro_crates/workflow-1728-1.crate/validation' \
    -H 'accept: application/json' \
    -H 'Content-Type: application/json' \
    -d '{
    "minio_config": {
      "accesskey": "<as_per_.env>",
      "bucket": "ro-crates",
      "endpoint": "minioSubmission:9000",
      "secret": "<as_per_.env>",
      "ssl": false
    },
    "profile_name": "five-safes-crate"
  }'
  

  The response returned HTTP status 202, with the following body:

  {
    "message": "Validation in progress"
  }
  

  This was the expected result.

• Once the validation had been triggered, I retrieved the result using the validator API GET endpoint. The corresponding curl command was:

  curl -X 'GET' \
    'http://localhost:5001/v1/ro_crates/workflow-1728-1.crate/validation' \
    -H 'accept: application/json' \
    -H 'Content-Type: application/json' \
    -d '{
    "minio_config": {
      "accesskey": "<as_per_.env>",
      "bucket": "ro-crates",
      "endpoint": "minioSubmission:9000",
      "secret": "<as_per_.env>",
      "ssl": false
    }
  }'
  

  The response contained a list of validation issues found in the crate, which was also expected:

  {
    "issues": [
      {
        "check": {
          "description": "Check if the file descriptor is in the **compacted** JSON-LD format",
          "identifier": "ro-crate-1.1_2.1",
          "label": "REQUIRED 2.1",
          "name": "Validation of the compaction format of the file descriptor",
          "order": 1,
          "requirement": {
            "description": "The file descriptor MUST be a valid JSON-LD file",
            "identifier": "ro-crate-1.1_2",
            "name": "File Descriptor JSON-LD format",
            "order": 2,
            "profile": {
              "description": "RO-Crate Metadata Specification.",
              "identifier": "ro-crate-1.1",
              "name": "RO-Crate Metadata Specification 1.1",
              "uri": "https://w3id.org/ro/crate/1.1"
            }
          },
          "severity": "REQUIRED"
        },
        "message": "The 9 occurrences of the JSON-LD key \"dct:conformsTo\" are not allowed in the compacted format because it is not present in the @context of the document",
        "severity": "REQUIRED",
        "violatingEntity": null,
        "violatingProperty": null,
        "violatingPropertyValue": null
      },
      "..."
    ],
    "meta": {
      "version": "0.2"
    },
    "passed": false,
    "validation_settings": {
      "abort_on_first": false,
      "enable_profile_inheritance": true,
      "profile_identifier": "five-safes-crate-0.4",
      "requirement_severity": "REQUIRED",
      "rocrate_validator_version": "0.8.1"
    }
  }
  

Overall, this confirmed that communication between the validator and MinIO was working as expected: the validation could be triggered through the API, and the validation results could be retrieved successfully.