🗺️Connection improvements

1 August 2023

`zli v. 6.27.4`

Connection failover. With this zli release, connections to targets can failover safely in the event of an outage in a particular AWS region. If an outage should occur, you should not experience any disruption to your connections. In order to take advantage of this new capability, you must be running a minimum of zli v. 6.27.0 and bzero v. 8.0.0

Microsoft SQL Server. Connecting to a SQL Server target with the Windows zli will open SQL Server Management Studio if installed
Windows RDP. Connecting to an RDP target with the Windows zli will launch the Remote Desktop Connection application (mstsc) unless the noAppStart flag is specified
Color theme. To support Powershell users, the zli's font colors have been modified to be friendly to all users regardless of which OS they are running

Invalid and incorrect commands. Resolved issue with invalid and incorrect commands not returning any message; now returns an error message and in cases where no arguments are provided, the help menu
Connect to RDP targets on Windows zli. Resolved issue when running the zli on Powershell that prevented the user from seeing the port number to connect to an RDP target (due to the color of the message the zli printed)
Debug daemon issues. Kubernetes, DB, and web daemons can be started in the foreground with the --debug flag, which allows additional information to be surfaced for more accurate troubleshooting
Web daemon and query parameters. Resolved an issue with the web daemon when handling query parameters

Connection failover. With this bzero release, connections to targets can failover safely in the event of an outage in a particular AWS region. If an outage should occur, you should not experience any disruption to your connections. In order to take advantage of this new capability, you must be running a minimum of zli v. 6.27.0 and bzero v. 8.0.0

send-logs for Kubernetes agents. bzero v. 8.0.3 enables zli send-logs to send both the previous and current container logs to assist in troubleshooting for Kubernetes agents

nodeSelector in Helm chart. Resolved inability to use nodeSelector as a value in the Helm chart due to spacing error. As a reminder, Helm does not automatically update the Helm chart when there are changes. To consume this fix, run helm repo update bastionzero to update to the latest chart version.
[Released 19 July 2023] RBAC and port forwarding. Resolved an issue seen in clusters that caused the agent to crash due to a user attempting to start a port forwarding session to a pod but only having get and not create RBAC permissions

Connection failover. This backend release contains the changes necessary to support connection failover. In order to take advantage of this new capability, you must be running a minimum of zli v. 6.27.0 and bzero v. 8.0.0

Targets API. Improved the targets API so all targets coming from Target Connect policies are based on what the associated agent type supports. ConnectionState can be used to query for targets by a specific connection state; if no parameter is provided, defaults to ConnectionState.Open
send-logs for Kubernetes agents. This backend release contains the changes necessary to support zli send-logs for Kubernetes agents including previous and current container logs

Agent healthcheck. Resolved an issue where an agent can be in contact with a connection node but still be marked as offline
Target status error message. When trying to connect to a target by target-name, target-name.environment, or target-name.environment-id that is offline, BastionZero now returns an error message that a target by that name was found but is unable to be connected to because it is offline
Powershell autodiscovery script. Resolved a typo in the Powershell autodiscovery script

For questions or to provide feedback on how we can improve our updates, reach out to product@bastionzero.com.

Last updated 1 year ago