« Changelog History


Kong v0.14.1 Release Notes

  • 🚀 > Released on: 2018/08/21

    ➕ Additions

    🔌 Plugins
    • 👍 jwt: Support for tokens signed with HS384 and HS512. Thanks @kepkin for the patch. #3589
    • acl: Add a new hide_groups_header configuration option. If enabled, this option prevents the plugin from injecting the X-Consumer-Groups header into the upstream request. Thanks @jeremyjpj0916 for the patch! #3703

    🛠 Fixes

    Core
    • 🔌 Prevent some plugins from breaking in subtle ways when manipulating some entities and their attributes. An example of such breaking behavior could be observed when Kong was wrongly injecting X-Consumer-Username: userdata: NULL in upstream requests headers, instead of not injecting this header at all. #3714
    • 🛠 Fix an issue which, in some cases, prevented the use of Kong with Cassandra in environments where DNS load-balancing is in effect for contact points provided as hostnames (e.g. Kubernetes with cassandra_contact_points = cassandra). #3693
    • 🛠 Fix an issue which prevented the use of UNIX domain sockets in some logging plugins, and custom plugins making use of such sockets. Thanks @rucciva for the patch. #3633
    • 👷 Avoid logging false-negative error messages related to worker events. #3692
    CLI
    • 🛠 Database connectivity errors are properly prefixed with the database name again (e.g. [postgres]). #3648
    🔌 Plugins
    • zipkin
    • basic-auth: Passwords with whitespaces are not trimmed anymore. Thanks @aloisbarreras for the patch. #3650
    • hmac-auth: Ensure backward compatibility for clients generating signatures without the request's querystring, as is the case for Kong versions prior to 0.14.0, which broke this behavior. Users of this plugin on previous versions of Kong can now safely upgrade to the 0.14 family. Thanks @mlehner616 for the patch! #3699
    • ldap-auth
      • Set the WWW-Authenticate header authentication scheme accordingly with the conf.header_type property, which allows browsers to show the authentication popup automatically. Thanks @francois-maillard for the patch. #3656
      • Invalid authentication attempts do not block subsequent valid attempts anymore. #3677

    Back to TOC