Hi. That K article sounds like the issue we are experiencing.
Now, we have the same issue not only on the ASM module, but also when trying to create a APM API protection profile. Same error message: "/var/config/rest/downloads/openapi.json is not a valid OpenAPI spec file.".
The openapi spec file is in version 3.0.2 and used with other tools without issues.
Furthermore, we now also have an F5 running 16.1.3. Again, when creating an API protection profile on APM it fails. This time with the error message: "java.net.ProtocolException: status:400, body:{"code":400,"message":"transaction failed:\"the\" unknown property","errorStack":[],"apiError":2}".
What's wrong with our approach?
BR,
Raphael