#MAGIC HIDER 1.3.1 HOW TO#
Refer to the upgrade guide for 3.2 for all session configuration changes and guidance on how to convert your existing session configuration. Although your configuration will continue to work as previously configured, we recommend adjusting your configuration to avoid future unexpected behavior. Many session parameters have been renamed or removed.Unless configured differently, sessions expire after 86400 seconds (24 hours). The new parameter absolute_timeout has a default value of 86400.Unless configured differently, sessions expire after 900 seconds (15 minutes) of idling. The new parameter idling_timeout, which replaces cookie_lifetime, now has a default value of 900.During that time, the invalid sessions could cause failures and partial downtime. This also affects any session configuration that uses the Session or OpenID Connect plugin in the background, including sessions for Kong Manager and Dev Portal.Īll existing sessions are invalidated when upgrading to this version.įor sessions to work as expected in this version, all nodes must run Kong Gateway 3.2.x or later.įor that reason, we recommend that during upgrades, proxy nodes with mixed versions run forĪs little time as possible. This library is used by the following plugins: Session, OpenID Connect, and SAML.
#MAGIC HIDER 1.3.1 FULL#
This version includes a full rewrite of the session library, and is not backwards compatible. The lua-resty-session library has been upgraded to v4.0.0. The JWT plugin now denies any request that has different tokens in the JWT token search locations.If you were previously relying on the Kong-Debug header to provide debugging information, set allow_debug_header: on to continue doing so. TLS versions lower than tlsv1_2 are already deprecated and considered insecure from PostgreSQL 12.x onward.Ĭonfiguration property to nf to constrain the Kong-Debug header for debugging. To use the default setting in nf, verify that your Postgres server supports TLS 1.2 or higher versions, or set the TLS version yourself. This mirrors the setting ssl_min_protocol_version in PostgreSQL 12.x and onward.įor more information about that parameter. Constrained the valid values of this configuration option to only accept the following: tlsv1_1, tlsv1_2, tlsv1_3 or any.The default PostgreSQL SSL version has been bumped to TLS 1.2.
We will stop building Alpine images and packages in Kong Gateway 3.4. These images and packages are available in 3.2 and will continue to be available in 3.3. Kong is announcing our intent to remove support for Alpine images and packages later this year.
#MAGIC HIDER 1.3.1 INSTALL#
To avoid this error, manually download the package from and install it.ĭeprecated Alpine Linux images and packages. The package is signed, however, it’s signed with a different (rotated) key from the metadata service, which triggers the error in yum. Due to changes in GPG keys, using yum to install this release triggers a Public key for kong-enterprise-edition-3.2.1.0. is not installed error.We plan to add the plugin back with the issues fixed in a later release. Datadog Tracing plugin: We found some late-breaking issues with the Datadog Tracing plugin and elected to remove it from the 3.2 release.The SAML plugin can now handle the field session_auth_ttl (removed since 3.2.0.0).The SAML plugin now works on read-only file systems.This file was missing in all 3.x versions of Kong Gateway prior to this release. Added the default logrotate file /etc/logrotate.d/kong-enterprise-edition.In Kong 3.2.1.0 and 3.2.1.1, alpine and ubuntu ARM64 artifacts incorrecty handled HTTP2 requests, causing the protocol to fail.Alpine deprecation reminder: Kong has announced our intent to remove support for Alpine images and packages later this year.Due to a build system issue, Kong Gateway 3.2.x packages prior to 3.2.2.1 didn’t contain the debug symbols that Dynatrace requires.
0 kommentar(er)
