[Bug]: Regression in REST Connection metadata: API Key header not applied when sending requests in 2.17; additional error when Test URL is empty

[CarlosJuncher03]

Apache Hop version?

2.17

Java version?

17

Operating system

Windows

What happened?

In version 2.17, when configuring a REST connection via metadata using an API key (setting the header name and value, e.g., Authorization: Bearer ), the header value is not validated/applied when the request is sent to the API.

If I change the authentication method to Basic Authentication and provide username/password, the request works.

Additionally, if the Test URL field is left blank, Hop fails to test/validate the connection.

Steps to reproduce

Open Hop 2.17.

Create/edit Metadata → REST Connection.

Select authentication by API key.

Fill in:

Header name: Authorization (or any other)

Header value:

If you create a rets connection in 2.16, it won't work in 2.1

Issue Priority

Priority: 3

Issue Component

Component: Hop Gui

[CarlosJuncher03]

Regarding the error message that appears when the REST URL is empty, I recommend removing it and adding the handling from version 2.16, which validates the base URL when the test URL is empty.

[gmitter-ef]

we can verify this bug, happened when trying to authenticate using 2.17 ==> error. 2.16 works. The "API key" label is also a little confusing.

[CarlosJuncher03]

In version 2.17, a change occurred: what was generated as a header in version 2.16 (e.g., Authorization) now appears as an API key in the metadata. The intention is to specify the header name and value (e.g., Authorization: Basic ), however, this configuration via API key is not being applied correctly in the request.

Important: In version 2.17, using the native basic authentication method (username/password), authentication works normally. The problem occurs specifically when we try to send the same content via API key.

Note: The test URL is working perfectly, thank you. The error I mentioned above is the same one gmitter-ef commented on.