Hi,
we are using jsign within a Maven Multi-Module Project. The object sigining certificate is issued with our own PKI. To access the timestamping server we have to use the company's proxy server.
The proxy is configured in settings.xml and all hosts in the local network are excluded in nonProxyHosts. Nevertheless jsign tries to load PKI certificates from the proxy server, and even worse all Maven artifacts in our private Nexus server cannot be resolved, because our proxy returns 403 for local servers.
jsign-maven-plugin reads the proxy host and port from settings.xml, but not nonProxyHosts. SignatureHelper uses these setting swith ProxySelector. So all subsequent http requests for the whole VM are sent to the proxy server.
As a workaround I had to remove the proxy server from settings.xml and set the Java networking properties with system properties.
Hi,
we are using jsign within a Maven Multi-Module Project. The object sigining certificate is issued with our own PKI. To access the timestamping server we have to use the company's proxy server.
The proxy is configured in settings.xml and all hosts in the local network are excluded in nonProxyHosts. Nevertheless jsign tries to load PKI certificates from the proxy server, and even worse all Maven artifacts in our private Nexus server cannot be resolved, because our proxy returns 403 for local servers.
jsign-maven-plugin reads the proxy host and port from settings.xml, but not nonProxyHosts. SignatureHelper uses these setting swith ProxySelector. So all subsequent http requests for the whole VM are sent to the proxy server.
As a workaround I had to remove the proxy server from settings.xml and set the Java networking properties with system properties.