You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 8, 2024. It is now read-only.
Support for remote (http) and local file references in OAS 2 and 3 schemas along with API Blueprint's Schema keyword.
For example, a schema such as:
{
"$ref": "./api/attribute.yaml#/attribute"
}
This particular feature needs a lot of thought as it can allow potential security problems for example when you run Dredd against an API Blueprint or OpenAPI document which contains a remote $ref in a schema. The $ref could potentially be used to populate a request body with sensitive data such as /etc/shadow, ~/.npmrc, ~/.ssh/id_rsa etc. This is the particular reason why this has been been supported. JSON Schema can be used to generate request and response bodies.
Support for remote (http) and local file references in OAS 2 and 3 schemas along with API Blueprint's
Schema
keyword.For example, a schema such as:
This particular feature needs a lot of thought as it can allow potential security problems for example when you run Dredd against an API Blueprint or OpenAPI document which contains a remote
$ref
in a schema. The$ref
could potentially be used to populate a request body with sensitive data such as/etc/shadow
,~/.npmrc
,~/.ssh/id_rsa
etc. This is the particular reason why this has been been supported. JSON Schema can be used to generate request and response bodies.Additional context
Raised from #1329 (comment)
The text was updated successfully, but these errors were encountered: