-
Print
-
DarkLight
This page contains release notes for Autify Connect. To view the release notes for the entire Autify for Web, please refer to Release notes.
v1.1.2 (March 14, 2023)
- Changed to follow redirection when a proxy indicates.
v1.1.1 (March 13, 2023)
--experimental-no-ssl-verify
flag is added.
v1.1.0 (March 13, 2023)
- This version is yanked.
v1.0.6 (February 20, 2023)
- Internal development workflow has been improved.
v1.0.5 (January 16, 2023)
- Internal development workflow has been improved.
v1.0.4 (January 10, 2023)
- Upgraded the internal library version.
v1.0.3 (December 19, 2022)
- Upgraded the internal library version.
v1.0.2 (December 13, 2022)
- Bug Fix: 401 connection failures
If you see the following type of error, please upgrade to v1.0.2 or later:WARN Initial connect to the Autify connect server failed: getting an unexpected status code 401 WARN Reconnect to the Autify connect server failed: getting an unexpected status code 401.
- Upgraded the internal library version.
v1.0.1 (December 1, 2022)
- Upgraded the internal library version.
v1.0.0 (November 29, 2022)
- This is the first major release of Autify Connect Client! 🎉
- Removed support for Autify Connect Client version v0.7.1 and below
- If you see the following message, please upgrade your Autify Connect Client
2022-11-29T15:56:01.888+0900 WARN Your version v0.6.8 is unsupported. Please install the latest stable version via https://help.autify.com/docs/setup-autify-connect again.
- If you see the following message, please upgrade your Autify Connect Client
- Removed the following deprecated flags
--experimental-sut-proxy
Please use the--sut-proxy
flag instead.—-experimental-tunnel-proxy
Please use the--tunnel-proxy
flag instead.--experimental-debug-server-port
Please use the--debug-server-port
flag instead.
v0.7.4 (November 15, 2022)
- Improved internal processes related to communication.
v0.7.3 (November 14, 2022)
- Improved the handshake process to establish a secure tunnel connection. This contributes to the speed of reconnection from Autify Connect Client to the server.
v0.7.2 (November 9, 2022)
- The message format returned by the server has been changed.
Support for Autify Connect Client v0.7.1 and lower will end on November 29, 2022.
v0.7.1 (November 8, 2022)
-
We fixed a bug in our official Docker image where connections would fail with the error “x509: certificate signed by unknown authority”.
If you see the following network error while using the Docker image, please consider upgrading to version v0.7.1 or later.
Reconnect to the Autify connect server failed: error on getting the handshake endpoint: Get "https://connect.autify.com/control/destination": x509: certificate signed by unknown authority.
v0.7.0 (November 8, 2022)
-
The following experimental flags have now been released as a stable feature.
-
--experimental-sut-proxy
Please use the
--sut-proxy
flag instead. -
—-experimental-tunnel-proxy
Please use the
--tunnel-proxy
flag instead. -
--experimental-debug-server-port
Please use the
--debug-server-port
flag instead.
-
-
The three experimental flags above are now deprecated and will be removed in the v1.0.0 release.
-
We added a new endpoint
GET /tcp_connections
to the debug server launched by the option--experimental-debug-server-port
.The information provided by the new endpoint is the same as
GET /idles_conns
. -
The endpoint
GET /idles_conns
is now deprecated and will be removed in the v1.0.0 release. -
When you give an invalid key, your
autifyconnect
now shows a WARN message instead of an INFO message. -
When the version of
autifyconnect
you use isn’t supported by our Autify Connect server, it now shows an ERROR message instead of an INFO message.
v0.6.17 (November 7, 2022)
-
Modified the tunnel handshaking logic, and the DEBUG log message has been changed as follows:
# Before The address of Autify connect server is "wss://connect.autify.com/base/handshake". # After The address to establish a secure tunnel is "wss://connect.autify.com/base/handshake".
We’ve been working on updating the infrastructure architecture updating for reliability and scalability, and this internal change allows you to enjoy more stable test executions.
v0.6.16 (October 24, 2022)
- Added the new option
--experimental-sut-proxy
to proxy connection between Autify Connect Client and System under test (test target application).
v0.6.15 (October 13, 2022)
-
Some warning message have been updated.
- We amended the warning message when an
autifyconnect
is shut down due to revoking an access point key.
- We amended the warning message when an
v0.6.14 (October 5, 2022)
- Improvements have been made to the internal structure of the system.
v0.6.13 (October 4, 2022)
- Internal development workflow has been improved.
v0.6.12 (September 29, 2022)
- Improvements have been made to the internal structure of the system.
v0.6.11 (September 28, 2022)
- Improvements have been made to the internal structure of the system.
v0.6.10 (September 28, 2022)
- Made internal updates.
v0.6.9 (September 27, 2022)
- Improvements have been made to the internal structure of the system.
v0.6.8 (September 26, 2022)
- Internal development workflow has been improved.
v0.6.7 (September 26, 2022)
- Improvements have been made to the internal structure of the system.
v0.6.6 (September 21, 2022)
- Started to support Linux 32-bit and Windows 32-bit.
v0.6.5 (September 21, 2022)
- Internal development workflow has been improved.
v0.6.4 (September 18, 2022)
- Internal development workflow has been improved.
v0.6.3 (September 17, 2022)
-
Mitigated race condition when terminating via debug API
- When the debug server gets
POST /terminate
, it starts exiting the running process before finishing the HTTP response. Therefore, we have a race condition that the HTTP connection gets rejected before receiving all responses. This version fixes this problem.
- When the debug server gets
v0.6.2 (September 13, 2022)
- Added the new endpoint
POST /terminate
to the debug server launched by the option--experimental-debug-server-port
.
v0.6.1 (September 12, 2022)
- Added the new option
--experimental-tunnel-proxy
to proxy connection between Autify Connect client and Autify Connect server.
v0.6.0 (September 12, 2022)
- Made minor bug fixes.
v0.5.9 (September 12, 2022)
- Made an internal update so that Autify CLI can support
autify connect
commands. See Autify CLI README for the supported commands.
v0.5.8 (September 7, 2022)
- Added the new option
--experimental-debug-server-port
for debugging and monitoring. It would be helpful for users to debug and monitor their autify connect client.
v0.5.7 (September 6, 2022)
-
Fixed the error message, especially for users of UNIX-like OS (e.g., Darwin)
-
When the network of machines where the Autify Connect client runs is disconnected or disabled, the client doesn’t close the session and waits up to a particular time for the network to rerun. After that, the client output the following error log.
ERROR reader stopped due to an unexpected error {"session_id": "{sessionID}", "websocket_conn_id": "websocketConnID", "error": "read tcp {ip}->{gip}: read: operation timed out"}
-
We changed the level of the log entry to the “WARN” level from the “ERROR” level.
WARN WebSocket connection reader stopped. This is most likely because the network disconnected or switched. {"session_id": "{sessionID}", "websocket_conn_id": "websocketConnID", "error": "read tcp {ip}->{gip}: read: operation timed out"}
-
v0.5.6 (September 1, 2022)
- Upgraded the internal library version
v0.5.5 (August 9, 2022)
- Upgraded the internal middleware version