Connecting Clients

This tutorial will show you how to connect a taskt client to the web server.

1. Ensure that tasktServer is up and running. The socket manager will register on startup and handle all incoming websocket requests to /ws Note the IP and port (or localhost, if debugging locally) of the web application. For this example, the server is running in debug locally at https://localhost:44389/

   

2. Launch the taskt client and click the "Settings" button.

   

3. Enable the preferred settings, enter the socket address (ex. wss://[ip]:[port]/ws ) and click connect. Once connected you will see the connection state update. Sample settings provided below. Note, the key will be provided to the client by the server so that field should be left empty on initial connection.

   Note: these settings save to a settings file under My Documents\taskt\AppSettings.xml and can be automatically deployed with the client if required.

   

   • Server Connection Enabled: Whether the client is enabled to make server connections. If this box is not checked, the client will not connect to the server.

   • Automatically Connect On Startup: Determines whether the application will automatically attempt to connect to the server at startup.

   • Retry If Connection Fails: If a connection is closed or fails, the client will automatically keep attempting to reconnect

   • Bypass SSL Validation: If enabled, the client will not validate SSL certificates provided by the server.

What happens on connection?

The client passes a public key to the server on connection and each time it provides updates. If the server does not recognize the public key (or if key is invalid or empty) the server will issue a new key to the client and create a new client entry on the dashboard. Client entries are tracked by keys -- each issued key becomes a new client entry.