SDK: Deadlock bei Verwendung eines Authentifizierenden Proxies mit falschen Zugangsdaten [OpenCode 90]

Description of the bug:

Wenn man einen Proxy verwendet, der einen Benutzernamen und Passwort benötigt, geht das SDK scheinbar in ein Deadlock, wenn man falsche Credentials eingibt. Die Requests dauern endlos lange. Es sollte in so einem Fall eine Exception geworfen werden.

Beispielcode:

    var proxyConfig = ProxyConfig.builder()
                                         .host("proxyHost") // <- host und port müssen richtig sein
                                         .port(1234)
                                         .basicAuth(new ProxyAuth("wrongUser", "wrongPassword")) // <- passwort und/oder username sind falsch
                                         .build();

    var httpConfig = HttpConfig.builder().proxyConfig(proxyConfig).build();
    var config = ApplicationConfig.builder().httpConfig(httpConfig)
                                  // ... weitere Einstellungen ...
                                  .build();
    DestinationClient destinationClient = ClientFactory.createDestinationClient(config);
    destinationClient.listDestinations(0, 100); // <- hier deadlock

Current behavior:

Expected behavior:

Environments:

TEST, STAGE, PROD

Additional Information:

https://gitlab.opencode.de/fitko/feedback/-/issues/90

Dependency / relationship to other issues:

Responsible person / team:

Transfer history to different teams

Contact persons including contact details:

Screenshots / Logs / Requests:

Checklist:

• Add Severity label
• Add team label
• Related/affected issues/stories/epics linked and explained in the bug issue
• Creation of an automated test
• Bugfix deployed on DEV
• Bugfix tested on DEV
• Bugfix deployed on TEST
• Bugfix tested on TEST (possibly also by the connection project itself)
• Successful fix reported to Team Operations (Teams channel)
• Bugfix deployed on STAGE
• Bugfix tested on STAGE if necessary
• Bugfix deployed on PROD
• Bugfix tested on PROD (possibly also by the connection project itself)
• Final communication by Team Operations if necessary
• Internal documentation was checked and updated if necessary
• External documentation has been checked and updated if necessary
• Updated changelog if necessary

Approach/Solution:

Release version of the artifact: