I’m running across an issue with the API where the result is a missing route error. Here’s the error message for the security services, but the result is the same regardless of API endpoint:
Interestingly, when I use Swagger to test the endpoint, it works. Using curl from the eramba server itself or any other outside server fails with the error above. Note that the curl command was copied exactly from Swagger with the “-k” option added to ignore certificate errors.
I’ve validated permissions are correct for the API user account and attached screenshots showing both Swagger and curl results. The result is the same when using PowerShell and the “Invoke-RestMethod” cmdlet.
Swagger - Return Success
Curl - Return Error
EDIT: The application version is 3.19.1