The documentation of the SW360 client library states that either a specific proxy can be defined in the configuration of the HTTP client or no proxy will be used. Due to default settings applied by the underlying OkHttpClient, this is not correct: if not explicitly configured, OkHttpClient will use the global default proxy selector of Java (see https://square.github.io/okhttp/4.x/okhttp/okhttp3/-ok-http-client/-builder/proxy-selector/). So the library actually misses a setting to force a direct Internet connection.
This is also related to the configuration of the Compliance Tool: Here a flag proxyUse can be set; but even if set to false, the system proxy selector is used.
Summary of the Bug
The documentation of the SW360 client library states that either a specific proxy can be defined in the configuration of the HTTP client or no proxy will be used. Due to default settings applied by the underlying OkHttpClient, this is not correct: if not explicitly configured, OkHttpClient will use the global default proxy selector of Java (see https://square.github.io/okhttp/4.x/okhttp/okhttp3/-ok-http-client/-builder/proxy-selector/). So the library actually misses a setting to force a direct Internet connection.
This is also related to the configuration of the Compliance Tool: Here a flag proxyUse can be set; but even if set to false, the system proxy selector is used.