A connection for the agent represents the credentials for access to an external system. The connections within the agent are identified by name and typically consist of a url, a username and a password.

All credentials are encrypted with encryption AES with 256 bits and saved in the agent database. They are kept in clear memory only for the purpose of executing the relevant jobs. Once you have entered the credentials it is possible to modify them but they can not be visualized.

Connection Setup

Definition and maintenance of the list of connections managed by the agent is accessible navigating in the section Settings > Agents and selecting Connections tab .

Within the list you can view the details of a connection and to access the edit and delete buttons.

How to Test Connections

Inside the detail tab of each connection it is possible to make a test in order to verify if it is possible to establish the connection with the saved parameters. The test cannot intercept any permission issues on the data structures.

In case of a positive outcome we will be able to see a “OK” message. In this case the connection is properly configured and ready to use. There are no networking issues: the system can be reached.

In case of failure the error message will be specific depending on the driver implementation in use. Depending on the type of error test reachability from a network perspective and/or re-enter the correct credentials.

Connections to Blindata

A particular type of connection managed by the agent is the “Blindata”. This type of connection is used to specify access credentials to be used in the results upload procedures.

These credentials must have the appropriate permissions depending on the type of tasks to be carried out.

JDBC connections

JDBC connections allow the agent to access external databases through a JDBC driver. Use this connection type when the agent must connect to relational databases such as PostgreSQL, MySQL, SQL Server, or other JDBC-compatible systems.

When creating or editing a JDBC connection, complete the fields shown in the form below:

• Name: A descriptive label for the connection.
• Type: Set to JDBC.
• URL / Endpoint: The full JDBC connection string, for example jdbc:postgresql://localhost:5432/postgres.
• Driver Class Name: Specify the JDBC driver class to use when one is required by the connector.
• Username: The database login user.
• Password: The database login password.

How to add JDBC connection properties

Open the Advanced settings section to add custom properties and files:

• Add JDBC property: Use this to pass driver-specific settings such as timeouts, schema, or application name.
• Add secret property: Use this to reference sensitive values that should not be stored directly in the main form.
• File attachments: Upload secret files such as SSL certificates, key stores, or JSON credentials required by the JDBC driver.

How to upload a secret file for a JDBC connection

If your JDBC connection requires an external secret file, add it under File attachments. Common examples include:

• SSL certificate or key store files
• OAuth or service account JSON credentials
• Driver-specific credential files referenced by JDBC properties

Enter the relative file path to materialize the attachment, then upload the file content. The agent stores the file securely and uses it when establishing the JDBC connection.