GET /ping
in your API definition then only calls to GET /ping
will ignore the authentication step: calls to GET /Ping
or GET /PING
will require authentication. You can configure the middleware to be case insensitive at the endpoint level.
You can also set case sensitivity for the entire Tyk Gateway in its configuration file tyk.conf
. If case insensitivity is configured at the gateway level, this will override the endpoint-level setting.
operationId
defined in the OpenAPI Document that declares both the path and method for which the middleware should be added. Endpoint paths
entries (and the associated operationId
) can contain wildcards in the form of any string bracketed by curly braces, for example /status/{code}
. These wildcards are so they are human readable and do not translate to variable names. Under the hood, a wildcard translates to the “match everything” regex of: (.*)
.
The ignore authentication middleware (ignoreAuthentication
) can be added to the operations
section of the Tyk OAS Extension (x-tyk-api-gateway
) in your Tyk OAS API Definition for the appropriate operationId
(as configured in the paths
section of your OpenAPI Document).
The ignoreAuthentication
object has the following configuration:
enabled
: enable the middleware for the endpointignoreCase
: if set to true
then the path matching will be case insensitiveGET /anything
endpoint. Any such calls will skip the authentication step in the Tyk Gateway’s processing chain.
GET /Anything
will not skip authenticationignored
object to the extended_paths
section of your API definition.
The ignored
object has the following configuration:
path
: the endpoint pathmethod
: this should be blankignore_case
: if set to true
then the path matching will be case insensitivemethod_actions
: a shared object used to configure the mock response middlewaremethod_actions
object should be configured as follows, with an entry created for each allowed method on the path:
action
: this should be set to no_action
code
: this should be set to 200
headers
: this should be blankGET /status/200
endpoint. Any such calls will skip the authentication step in the Tyk Gateway’s processing chain.
GET /Status/200
will not skip authenticationignored
object within the extended_paths
section of the API Definition.
In the example below the ignore authentication middleware has been configured for requests to the GET /get
endpoint. Any such calls will skip the authentication step in the Tyk Gateway’s processing chain.
GET /Get
will also skip authentication