Datasource connection test failed : 'Invalid file path: '

This behavior has been introduced in Elements Connect version 8.0.2.

Case A - Part of the path is defined in the datasource configuration and completed at the field level

Symptoms

You are using a File datasource, with the following configuration:

• Path defined in the datasource:

  CODE

  /opt/atlassian/jira/

• Path defined in field:

  CODE

  json_file.json

The Test connection fails on the datasource administration screen:

However, the field is still returning and displaying results correctly:

Cause

This behavior occurs because the datasource tester is designed to validate the complete path (including the file itself), not just part of it.

As a result:

• The test connection fails

• While the field still works correctly

Resolution

No action is required if the field is already working correctly.

Case B - The entire path is defined in the datasource configuration

Symptoms

You are using a File datasource, with the following configuration:

• Path defined in the datasource:

  CODE

  /opt/atlassian/jira/json_file.json

• Path defined in field:

  CODE

  $body

The Test connection fails on the datasource administration screen:

Cause

Security has been enhanced and it is no longer possible to specify the entire path at the datasource level while leaving the path section empty in the field configuration.

This prevents malicious users from attempting to access unintended resources.

Resolution

Following the security optimisations introduced in version 8.0.2, the complete file path must now be split between the datasource and field configuration:

• Previous configuration:

  • Datasource:

    CODE

    /opt/atlassian/jira/json_file.json

  • Field:

    CODE

    $body

• New configuration:

  • Datasource:

    CODE

    /opt/atlassian/jira/

  • Field:

    CODE

    json_file.json