Tyk Open Source API Gateway written in Go, supporting REST, GraphQL, TCP and gRPC protocols
OTHER License
Bot releases are hidden (Show)
Published by ilijabojanovic almost 2 years ago
Published by ilijabojanovic almost 2 years ago
Published by ilijabojanovic almost 2 years ago
Published by ilijabojanovic almost 2 years ago
Published by ilijabojanovic about 2 years ago
security.private_certificate_encoding_secret
did not default to the expected valueTYK_DB_HTTPSERVEROPTIONS_CERTIFICATES
environment variable was not setPublished by buger about 2 years ago
security.private_certificate_encoding_secret
did not default to the expected valueTYK_DB_HTTPSERVEROPTIONS_CERTIFICATES
environment variable was not setPublished by buger about 2 years ago
ports_whitelist
client_certificates
list allowed any certificate to be used against MTLS API.true
and no longer rely on param_name
and cookie_name
being non empty.Published by buger about 2 years ago
ports_whitelist
client_certificates
list allowed any certificate to be used against MTLS API.true
and no longer rely on param_name
and cookie_name
being non empty.Published by buger about 2 years ago
Published by ilijabojanovic about 2 years ago
http_server_options.enable_strict_routes
or environment variable TYK_GW_HTTPSERVEROPTIONS_ENABLESTRICTROUTES
is set to be true
.basic_auth_hash_key_function
to bcrypt
, sha256
or murmur64
, murmur128
. This is a backward compatible change with default being bcrypt
.enforce_org_data_detail_logging
is enabledPublished by sedkis over 2 years ago
Published by buger over 2 years ago
Published by buger over 2 years ago
security.hide_login_failure_limit_error
, which hides the login retry attempts failure message "Retry in N seconds", as exposing the number of seconds can be seen as a vulnerability.security.enforce_password_history
configuration option was enabled.{{.object.name}}
) won't remove the quotes of a string in UDG resulting in undesired behavior like in URL paths /user/"johndoe"
Published by buger over 2 years ago
use_param
and param_name
fields to the auth token signature configuration, in order to be able to pass the signature as a query parameter.@extends
directive alongside “extend” keyword - both provide the same behaviour when useddisable_query_batching
in API definition that controls if federation uses batching for GQL queries or not - users can choose if they want the queries to be executed with batching or not (this is connected to solving N+1 problem in federation)@extends
directive for a type that was not defined in any other subgraphPublished by buger over 2 years ago
slave_options.rpc_cert_cache_expiration
Published by buger over 2 years ago
Fixed loading of APIs when dealing with large amount (>2000 APIs)
For Hybrid Gateways added a way to configure interval for synchronizing analytics data: analytics_config.purge_interval
. Default 10 seconds.
Fixed getting and setting session inside Go plugins
Fixed loading same Go plugin bundle for Multiple APIs
Go plugin compiler now accepts second argument which allow setting plugin ID: `<plugin_name> <plugin_id>.
Go plugin "unique" names are based on file names. E.g. two plugins called "plugin.so" will look like the same plugin from Tyk point of view. You need need to use unique names for different plugins, or with new change, use new optional plugin_id argument, to specify plugin unique ID. Like this: docker run --rm -v
pwd:/plugin-source tykio/tyk-plugin-compiler:v3.2.3 plugin.so my_unique_plugin
Published by buger over 2 years ago
Our next major release is here!
End-to-end support for your enterprise GraphQL journey through Tyk’s Federated gateway, bringing Federated Subscriptions for the first time on any APIM platform, and supporting PostgreSQL for your data management needs!
Read full annoucement and release notes
https://tyk.io/releases/v4-0/
https://tyk.io/docs/release-notes/version-4.0/
Published by buger almost 3 years ago
{“use_param”: true, “param”: “foo”}
http_server_options.ssl_certificates
optionPublished by lghiur almost 3 years ago
403: Attempted access with non-existent cert.
. Access to an API is now authorised again, by just providing the authorisation header together with the key value, when the token is generated based on a provided certificate. https://github.com/TykTechnologies/tyk/pull/3704.Published by buger about 3 years ago
If you're upgrading from Tyk Gateway/Dashboard 3.2.1, due to packaging bug introduced in those versions, after doing upgrade, you need to run systemctl daemon-reload
(this command also mentioned in logs during upgrade as well).
enable_health_checks
option is deprecated, and going to be disabled by default starting from 4.0.0.
This option enable special API level health check endpoint, with was no longer used, and duplicate information provided by Tyk Pump.
Note that it is not related to Gateway health check endpoint. This option can cause significant performance issues, so ensure that you have it turned off in your installation, if not used.