12 Commits (e942db3dbc67abe6e128dbb47ed16db8e2a023de)

Author	SHA1	Message	Date
Justin Nguyen	dc7f0b00fc	Merge pull request #6207 from hashicorp/llb-password-credential-type ... Password credential type	3 months ago
dani	08015e9d98	feat(clientproxy): automatically close boundary connect when proxy is no longer in use (#6232) ... Co-authored-by: Andrew Gaffney <andrew@gaffney.cc>	3 months ago
Justin Nguyen	1ac444d0a8	feat(cli): Add support for password credential in redis helper (#6213)	3 months ago
dani	5ebf11caeb	create a deferral to automatically close sessions after creating them during boundary connect (#6054)	5 months ago
Hugo	2316fecbd6	Remove nhooyr.io/websocket from Boundary (#5992)	6 months ago
Damian Debkowski	9576ed40dc	test: improve test to ensure ipv6 compatability (#5113)	1 year ago
Todd	5ff3216565	Instead of relying on termination reason use status (#4852) ... * Instead of relying on termination reason use status Co-authored-by: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com>	2 years ago
Todd	98b5e3fa52	Close proxy listener if session is no longer active (#4850) ... * Close proxy listener if session is no longer active	2 years ago
Todd	6c378e7723	Create an option to set the session teardown timeout (#4834)	2 years ago
Elim Tsiagbey	1b1c8b3bf9	fix: Proxy closing listener with 0 connections left (#4389) ... * fix: Proxy closing listener with 0 connections left A bug was introduced in `0.15.0` where sessions with max connection counts were closed when the connections left hit 0. This issue was highlighted by a user: https://github.com/hashicorp/boundary/issues/4364. What was happening was when we have zero connections left the proxy code was closing the listener which closed its connections To fix this: - `boundary connect -target-id=xx -host-id=xx` command with no connections left will now wait for all connections to be closed and before exiting the session just like it did in `0.14.3` - As soon as there are no more connections left, the listener will close to stop accepting new connections - Fix issue where the websocket connection was throwing closing errors during the session teardown.	2 years ago
Jeff Mitchell	fff5f9506f	Migrate proxy logic to the API package (#4216) ... This allows arbitrary programs to have an easy mechanism to make connections through Boundary using Go. Internal cluster tests and test helpers have been migrated to use this package, as well as the `connect` command. --------- Co-authored-by: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com>	2 years ago
Jeff Mitchell	fb4a5a98dc	Add some target fields and move some things around (#3879) ... In preparation for putting proxy code in the api package this creates some necessary fields in the target output and it pre-moves credential parsing and proxy handshake code to their new places. This will make the diff for the actual proxy code move quite a bit smaller. Co-authored-by: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com>	2 years ago