Releases: warp-tech/warpgate
Releases · warp-tech/warpgate
v0.6.5
Changes
- f967609: Added unattended setup command (
warpgate unattended-setup
) - fixes #409 - 7066dd5: Added password recovery command (
warpgate recover-access
) - fixes #410 - Added option to forward username to SSH targets as-is #445 (Alex Donec)
- Removed the 1 second auth delay on SSH - #459 (Eugene Pankov)
- c236da5: Added support for MySQL and PostgreSQL as database storage (
database_url
config option) - fixed #452
UI improvements
- 67866fe: added visual feedback to save buttons
- fd993c4: autofocus the OTP field - fixes #386
- 5bdddd3: allow cancelling authentication
Fixes
v0.6.4
v0.6.3
v0.6.2
v0.6.1
Major updates
- Targets, roles and users are now stored in the database instead of the config file
- Your existing data will be automatically migrated into the database
- To stave off the migration, set
config_provider: file
on the top level of your config file. File based target configuration will be removed in v0.7 however.
Changes
v0.5.1
v0.5.0
Major updates
- Added SSO support (OpenID Connect) for HTTP and SSH targets (#222)
- Added support for linking HTTP targets to subdomains
- HTTP: added support for tickets (as a GET parameter or Authorization header)
Changes
- HTTP: added
X-Forwarded-*
headers - HTTP: session cookie is now set for all subdomains
- UI: added proper connection instructions for tickets
- UI: added
test-target
CLI support for HTTP and MySQL targets - SSH: added support for AES-CTR ciphers, and diffie-hellman exchanges
- Sessions will be automatically killed if you revoke access by editing the config file
- Fixed
scp
not triggering target connection
v0.4.1
- fixed RSA public keys not getting accepted
v0.4.0
Major updates
- This release adds experimental support for MySQL targets. Check out Adding a MySQL target on the wiki. Also see Protocol support for limitations.
- All protocols are now disabled by default. If you've used
warpgate setup
to generate your config file, no action is needed. Otherwise add an explicitenable: true
for the protocols you need.
Changes
warpgate check
now checks certificates and keys- added TLS options for HTTP targets
- added
ssh.host_key_verification
setting that allows automatically accepting (auto-accept
) or rejecting (auto-reject
) unknown host keys
v0.3.0
Major updates
Warpgate now supports exposing HTTP(S) targets through the bastion in addition to SSH targets - see https://github.com/warp-tech/warpgate/wiki/Adding-an-HTTP-target
Migration notes
- ℹ️ The Docker image now needs a configuration file provided to it through a data volume - see Getting started on Docker
- ℹ️ The
web_admin
config key has been deprecated and renamed tohttp
, and the web admin UI itself is now a part of the HTTP protocol handler.