Release v0.29.0 · warp-tech/warpgate

Warpgate has released version 0.29.0, inviting users to provide feedback on their deployment and suggestions for improvements. The report notes that numerous proposed changes were influenced by user feedback through a recent survey.

This update introduces breaking API changes, implying existing API clients may no longer function correctly. Users are advised to utilize the compatible Terraform provider version v1.2.0 and Kubernetes operator v0.4.11 for seamless integration.

A new feature enables the setup of targets that require an admin's approval before each session becomes active. This approval process can be customized with a configurable timeout and caching mechanism for approval.

Another significant addition is a global setting, allowing administrators to mandate or request the use of a second factor authentication for all users. An exception can be made for Single Sign-On (SSO) users. This policy is editable under Config → Policies and applies to all new users by default.

Kubernetes clients now receive precise reasons for certificate validation failures and potential database errors. If a user account is deleted and subsequently recreated, sessions for the deleted account persist within the system.

Additionally, open native protocol sessions for a deleted user remain active until explicitly closed. To stay updated, users are encouraged to subscribe to the major release notes as well as vulnerability alerts through email. Access the newsletter at https://warpgate.null.page/newsletter/.