Processing execution error - eoepca: pepresource.so service error

[rconway]

After initiating processing, a call to Get Execute Status indicates failure...

HTTP/1.1 200 OK 
Date: Mon, 06 Feb 2023 15:10:37 GMT
Content-Type: application/json;charset=UTF-8
Transfer-Encoding: chunked
Connection: close
X-Powered-By: ZOO@ZOO-Project
Strict-Transport-Security: max-age=15724800; includeSubDomains

{
  "jobID": "68324384-a630-11ed-86f6-ae7994252e72",
  "type": "process",
  "processID": "snuggs-0_3_0",
  "status": "failed",
  "message": "Unable to run the Service. The message returned back by the Service was the following: eoepca: pepresource.so service error return code: 0 on \/test\/watchjob\/processes\/snuggs-0_3_0\/jobs\/68324384-a630-11ed-86f6-ae7994252e72 ",
  "links": [
    {
      "title": "Status location",
      "rel": "status",
      "type": "application\/json",
      "href": "\/test\/wps3\/jobs\/68324384-a630-11ed-86f6-ae7994252e72"
    }
  ]
}

[rconway]

This implies that the ADES is expecting to receive a JWT - but has not received one.
The id_token must be passed as a Bearer in the ADES execute request.

The ADES has a couple of modes where it expects to receive a JWT as a Bearer token:

• workflowExecutor.wps.usePep - enables the ADES to interface with the pep to create dynamic protection for 'new' resources as they are created in the ADES. Set to false for simplicity.
• workflowExecutor.useResourceManager - instructs the ADES to interface with the workspace-api to register processing results with the user's workspace. Set to false for now until you have a workspace.

Also suggest that you use ADES chart 2.0.6 since there were some errors with the handling of these two config params that were fixed in this version.