- Print
- DarkLight
This page contains general Autify Connect FAQ, divided into security and networking sections. If you would like to check for information about common errors and tips please go to Autify Connect Common Errors.
Security issue FAQs
Can person A delete an access point created by person B?
Yes. Since access points are managed on the Workspace settings page, anyone with access to the Workspace settings page can delete them.
What happens if access point keys are leaked?
The only thing that an attacker can do is to launch the Autify Connect client using the key. They cannot request any data using the key, nor retrieve any data stored in the closed network.
Can Autify Connect be used with Basic Authentication?
Providing your Autify Connect driven scenarios use the same domain as that configured for basic authentication in your workspace, there should be no problem!
For more details on how to set up basic authentication, refer to the “Do you support BASIC authentication?” FAQ.
When using Autify Connect, what is the source IP address?
When using Autify Connect, the source IP address for the test run will be the IP address of the environment in which the Autify Connect client is running. This is true for tests run on “real devices” (i.e BrowserStack) as well.
Can the same access point key be used on multiple terminals when running Autify Connect client?
No. If you want to run Autify Connect client on multiple terminals at the same time, you will need a separate access point key for each client.
Where can I check the release history of Autify Connect
You can check all release notes via the Autify Connect Release Notes page.
Networking related FAQs
How can I confirm that the Autify connection is ready for use?
After you input autifyconnect
in the command line, the following message will be shown if the connection was successful:
$ autifyconnect
2022-09-07T19:29:04.411+0900 INFO Successfully connected!
autifyconnect
readiness continuouslyIf you want to monitor the daemonized Autify Connect client and confirm that it is always running, please refer to the Check connection continuously section of the common Autify Connect errors and tips document.
How users can disconnect an Autify Connect client session (tunnel connection)
You have two ways to disconnect a session from the Autify Connect server.
- Kill the process of your Autify Connect client. e.g. Input Ctrl+C in your terminal console.
- Revoke the access key from the Autify Web UI. If this step is done, the Autify Connect client that uses that access key will shut down automatically. Revoking the access key can be done by deleting the key in the appropriate workspace.
Does Autify Connect make tests slower?
Test execution speed mainly depends on the customer’s network condition and device performance.
Technically, using Autify Connect will be slower because it adds a new network route compared to the normal test executions. However as far as we tested there is no significant time lag compared to test executions done without Autify Connect.
Are there any potential errors that may occur due to slower test execution?
There are two main patterns of test failures that may occur due to longer execution times:
- Slow page transition causes the next test step fail (e.g. Clicking A page element)
- Test results page shows a
ERR_TUNNEL_CONNECTION_FAILED
error (on Chrome/Linux)
Can I run tests with Autify Connect using a proxy server that exists between the Autify Connect Client and the Autify Connect Server?
Yes. For more information, see Configuration when using a Proxy server.
Can I run tests with Autify Connect using a proxy server that exists between the Autify Connect Client and the application under test?
Yes. For more information, see Configuration when using a Proxy server.
Can I use Autify Connect to test localhost websites?
Yes. Instructions on how to set up localhost
tests can be found at Autify Connect integration.
If your localhost test does not work, please refer to the I am not able to use Autify Connect to test websites running on localhost section of the Autify Connect troubleshooting guide.
When Autify Connect client is running, does it affect the communication of other tools running on the same terminal?
Autify Connect creates a private tunnel between Autify and the terminal on which Autify Connect client is running, so it does not affect the communication of other tools.
What communication protocol does Autify Connect use to establish a secure tunnel?
The Autify Connect client first communicates with the Autify Connect server via HTTPS to establish an initial connection. This connection is then upgraded to an encrypted WebSocket (WSS), ensuring secure communication. All interactions between the client and server occur over this encrypted WebSocket and remain active until the terminal window or background process running Autify Connect is closed.
How are test results stored when using Autify Connect during a test execution?
The Autify Connect server acts as a bridge, managing the communication between the Autify Connect client and the Autify App workers. Test results are stored in the same cloud storage used by Autify NoCode Web. There are no special steps or changes in how test results are handled when using Autify Connect.
How does the Autify Connect client communicate with the Autify App server?
The Autify Connect client connects to the Autify Connect server using a secure WebSocket connection. When a test is queued, the Autify App server communicates with the Autify Connect server, and all data flows securely through the WebSocket.
For more information, see how Test Execution works.
What are the character types and number of digits in the Autify Connect (access point) key?
An Autify Connect access point key is 30 characters long and consists of a mix of alphanumeric characters, including both uppercase and lowercase letters. It also includes 6 digits (numbers) for added complexity and security.
Is the source IP address processed when accessing the test environment from a real device?
The Autify Connect client acts like a local proxy on your computer. It follows instructions from the Autify Connect server to send a request and then returns the results without modifying them. How the request is handled on the network depends on the settings of the machine running the Autify Connect client. In essence, it behaves like a tool that sends requests directly from your device without altering the source IP address.
Why do I need to allow access to BrowserStack when using real devices or Win10/macOS with Autify Connect?
To use real devices or specific operating systems like Win10/macOS with Autify Connect, the Autify Connect client needs access to BrowserStack’s servers. This is required by BrowserStack for the connection to work smoothly. Even though this access is needed, all communication still flows securely through the Autify Connect client’s tunnel, ensuring your data is protected.
Can I use multiple terminals and environments with Autify Connect?
You can use either one terminal or multiple terminals with Autify Connect. However, each test plan can only have one Autify Connect key. If you’re using a single terminal, you can run multiple test plans with the same key. While it’s possible to run multiple Autify Connect client terminals on a single machine, you can only use one terminal client with a given key at a time. If you try to use the same key in another terminal, it will cause the first terminal to shut down.