Incompatibility with Hashicorp Vault 1.18.1, last working version is 1.16.1

[lgblaumeiser]

Describe the bug

As I recently found out, there is a general incompatibility with the Hashicorp Vault 1.18.1. The bug is actually on there side, but current connector versions are not able to work with this vault version. Last known version that works is 1.16.1.

Issue is, that the way, the upstream connector creates the url for a rest call, it uses encoded slashes, resp. %2F. According to the corresponding web standard a system should properly work with plain and encoded slashes, but version 1.18.1 does not. This way actually encountered in the test of the BDRS service, as the tests took the latest version of the vault which failed at some point consistently.

To Reproduce

1. Configure the deployment tests, of e.g., the BDRS, to use a vault 1.18.1 (resp. the corresponding helm chart)
2. Try to run the tests
3. Observe stange IOExceptions which indicate that an html page was returned at some point instead of a JSON object

Expected behavior

As the error is on the vault side, the only means is to use a working vault implementation

[ndr-brt]

JFYI, upstream the Hashicorp version used for integration tests has been bumped to 1.18.3, so this one is compatible with EDC, I don't know about 1.18.1, but should this considered a bug then?

[lgblaumeiser]

Solution: Make a remark in the Readme that this version will not work with the EDC as discussed in the weekly