github warp-tech/warpgate v0.12.0-beta.1

latest release: v0.12.0-beta.2
pre-release4 days ago

Changes

  • Self-service credentials management (#1145) - you can now allow users to manage their own credentials. Enable it in Config -> Misc -> Global parameters.
  • Multiple return domains for SSO, prefer host header over external_host (dbf96a8 / #1093) - Warpgate now users the Host header to resolve its own external URL and only falls back to the external_host from the config file if the header is missing. If you're running behind a reverse proxy, make sure that http.trust_x_forwarded_headers is set in the config and you're passing the X-Forwarded-Host header. SSO logins will also dynamically construct their return URL from the Host header. You can restrict the allowed return domains with the new sso_providers[].return_domain_whitelist option (a list of hostnames).
  • Passing user-identifying headers to HTTP targets (cc0b054 / #1107) - Warpgate now passes x-warpgate-username and x-warpgate-authentication-type headers to HTTP targets.
  • --enable-admin-token option (9dd1c58) - setting it allows passing a global admin token via the WARPGATE_ADMIN_TOKEN env variable. This token can be used to authenticate against the admin REST API (pass it in the x-warpgate-token header).

Other changes

Fixes

  • 846e6d1: fixed #1110 - Fix switch for insecure ssh algorithms option (#1111) (hashfunc)
  • 38dbb3b: fixed #1096 - SEC1 EC private key file support for TLS
  • 80ee6cc: fixed #1074 - strip trailing slash in SSO issuer URLs and log errors properly
  • 8acaaee: show more detailed error messages for API errors
  • 3b29a3e: fixed #929 - sso: broken additional_trusted_audiences config option
  • 557921f: postgres listener was incorrectly using the mysql certificate & key
  • 41d3158: fixed #1039 - first DB migration failing on Postgres

Don't miss a new warpgate release

NewReleases is sending notifications on new releases.