| [ Web Proxy ] |
| Viewing: https://developers.cloudflare.com/api/resources/api_gateway | [Back] [Original] |
Auth ID Characteristic extracted from JWT Token Claims
Claim location expressed as $(token_config_id):$(json_path), where token_config_id
is the ID of the token configuration used in validating the JWT, and json_path is a RFC 9535
JSONPath (https://goessner.net/articles/JsonPath/, https://www.rfc-editor.org/rfc/rfc9535.html).
The JSONPath expression may be in dot or bracket notation, may only specify literal keys
or array indexes, and must return a singleton value, which will be interpreted as a string.
The endpoint which can contain path parameter templates in curly braces, each will be replaced from left to right with {varN}, starting with {var1}, during insertion. This will further be Cloudflare-normalized upon insertion. See: https://developers.cloudflare.com/rules/normalization/how-it-works/.
API discovery engine(s) that discovered this operation
State of operation in API Discovery
review - Operation is not saved into API Shield Endpoint Managementsaved - Operation is saved into API Shield Endpoint Managementignored - Operation is marked as ignoredThe endpoint which can contain path parameter templates in curly braces, each will be replaced from left to right with {varN}, starting with {var1}, during insertion. This will further be Cloudflare-normalized upon insertion. See: https://developers.cloudflare.com/rules/normalization/how-it-works/.
The endpoint which can contain path parameter templates in curly braces, each will be replaced from left to right with {varN}, starting with {var1}, during insertion. This will further be Cloudflare-normalized upon insertion. See: https://developers.cloudflare.com/rules/normalization/how-it-works/.
The endpoint which can contain path parameter templates in curly braces, each will be replaced from left to right with {varN}, starting with {var1}, during insertion. This will further be Cloudflare-normalized upon insertion. See: https://developers.cloudflare.com/rules/normalization/how-it-works/.
OpenAPI JSON schemas for an operation, including both user-uploaded and Cloudflare-learned schemas.
An OpenAPI operation object fragment containing schema information for an operation. May include parameter definitions, request body specifications, and a component schema extension.
The endpoint which can contain path parameter templates in curly braces, each will be replaced from left to right with {varN}, starting with {var1}, during insertion. This will further be Cloudflare-normalized upon insertion. See: https://developers.cloudflare.com/rules/normalization/how-it-works/.
OpenAPI JSON schemas for an operation, including both user-uploaded and Cloudflare-learned schemas.
An OpenAPI operation object fragment containing schema information for an operation. May include parameter definitions, request body specifications, and a component schema extension.
The endpoint which can contain path parameter templates in curly braces, each will be replaced from left to right with {varN}, starting with {var1}, during insertion. This will further be Cloudflare-normalized upon insertion. See: https://developers.cloudflare.com/rules/normalization/how-it-works/.
The endpoint which can contain path parameter templates in curly braces, each will be replaced from left to right with {varN}, starting with {var1}, during insertion. This will further be Cloudflare-normalized upon insertion. See: https://developers.cloudflare.com/rules/normalization/how-it-works/.
The endpoint which can contain path parameter templates in curly braces, each will be replaced from left to right with {varN}, starting with {var1}, during insertion. This will further be Cloudflare-normalized upon insertion. See: https://developers.cloudflare.com/rules/normalization/how-it-works/.
The endpoint which can contain path parameter templates in curly braces, each will be replaced from left to right with {varN}, starting with {var1}, during insertion. This will further be Cloudflare-normalized upon insertion. See: https://developers.cloudflare.com/rules/normalization/how-it-works/.
The endpoint which can contain path parameter templates in curly braces, each will be replaced from left to right with {varN}, starting with {var1}, during insertion. This will further be Cloudflare-normalized upon insertion. See: https://developers.cloudflare.com/rules/normalization/how-it-works/.
The endpoint which can contain path parameter templates in curly braces, each will be replaced from left to right with {varN}, starting with {var1}, during insertion. This will further be Cloudflare-normalized upon insertion. See: https://developers.cloudflare.com/rules/normalization/how-it-works/.
The endpoint which can contain path parameter templates in curly braces, each will be replaced from left to right with {varN}, starting with {var1}, during insertion. This will further be Cloudflare-normalized upon insertion. See: https://developers.cloudflare.com/rules/normalization/how-it-works/.
When set, this applies a mitigation action to this operation
log log request when request does not conform to schema for this operationblock deny access to the site when request does not conform to schema for this operationnone will skip mitigation for this operationnull indicates that no operation level mitigation is in place, see Zone Level Schema Validation Settings for mitigation action that will be appliedWhen set, this applies a mitigation action to this operation
log log request when request does not conform to schema for this operationblock deny access to the site when request does not conform to schema for this operationnone will skip mitigation for this operationnull indicates that no operation level mitigation is in place, see Zone Level Schema Validation Settings for mitigation action that will be appliedWhen set, this applies a mitigation action to this operation
log log request when request does not conform to schema for this operationblock deny access to the site when request does not conform to schema for this operationnone will skip mitigation for this operationnull indicates that no operation level mitigation is in place, see Zone Level Schema Validation Settings for mitigation action that will be appliedThe default mitigation action used when there is no mitigation action defined on the operation
Mitigation actions are as follows:
log - log request when request does not conform to schemablock - deny access to the site when request does not conform to schemaA special value of of none will skip running schema validation entirely for the request when there is no mitigation action defined on the operation
Diagnostic warning events that occurred during processing. These events are non-critical errors found within the schema.
JSONPath location(s) in the schema where these events were encountered. See https://goessner.net/articles/JsonPath/ for JSONPath specification.
The endpoint which can contain path parameter templates in curly braces, each will be replaced from left to right with {varN}, starting with {var1}, during insertion. This will further be Cloudflare-normalized upon insertion. See: https://developers.cloudflare.com/rules/normalization/how-it-works/.
The endpoint which can contain path parameter templates in curly braces, each will be replaced from left to right with {varN}, starting with {var1}, during insertion. This will further be Cloudflare-normalized upon insertion. See: https://developers.cloudflare.com/rules/normalization/how-it-works/.
| Web Proxy Viewer | New URL | Original Page |