search

IS-AgroSmart / AgroSmart-Web

1 stars 1 forks source link

Flight never finishes processing #136

Closed jreyesr closed 3 years ago

jreyesr commented 3 years ago

With the introduction of authentication on NodeODM API calls, the webhook_adapter container can no longer ping the NodeODM API to monitor Flights, since the API rejects its requests with a HTTP 403 error.

This means that flights are forever stuck on 100% progress and the webhook is never called, which means that the Geoserver workspaces are never created, among other issues.

jreyesr commented 3 years ago

Proposed fix is to slightly relax the authentication code, only on the /nodeodm/task/uuid/info endpoint, so that requests coming from the IP of the webhook_adapter container bypass the authentication step.