How to debug HTTP Proxy problems with artifactory? - maven-2

I have an artifactory within a corporate network. I configured a http proxy for each remote repository. It doesn't work. How could I possibly find out why it doesn't work? Are there any log settings which I could tweak?
Using the same proxy within Firefox works just fine.

Artifactory 2 uses logback for logging, you can find its configuration in $ARTIFACTORY_HOME/etc/logback.xml
If you can access the repository through the browser, it's likely the problem is in your Maven configuration. If you've a proxy configuration defined, you'll need to ensure the proxy is set to exclude your internal http proxy server.
If you run Maven with the -X switch, it will give you more details on the connection attempts Maven is making.

Related

https requests from a Jenkins Job blocked

I'm experiencing an issue with https requests sent from a Jenkins job, which are blocked and do not reach the final server.
The scenario is as follows:
I have a server where I'm running some backend, exposing APIs both over http and https (it's a django + django rest framework backend)
I implemented a Rhinoceros Plugin in C#, which needs to perform some rest API requests to the above mentioned server
On another server, I'm running a Jenkins job that is responsible for compiling the plugin, installing it on Rhinoceros and run some operations on Rhinoceros for test purposes
All calls over http do work like a charm from the plugin running on the Jenkins job, but all https do not work.
NOTES:
When manually running the plugin outside Jenkins, the https remote request succeed without any issue
Moreover, https requests sent from any other location do work
When the plugin runs from the Jenkins job no trace of any incoming connection is logged into the backend server, so that makes me believe the request never leaves the Jenkins server
WHAT I TRIED:
I installed the domain certificate locally on the Jenkins server, using keytool, on the JAVA_HOME/lib/security/cacerts keystore
I tried to install some Jenkins Plugins to skip certificate check or to trust certain domains
I checked the firewall on the Jenkins machine (adding allow rules for both Java and Rhinoceros applications)
So far, nothing worked.
Any idea?
Thanks

maven deploy to nexus through SSO

I have nexus installed behind of apache server. apache is configured to use SSO, it's triggered in the apache level and then I pass uid through headers.
the problem is that does not work when I want to deploy to nexus with maven.
Have you any idea please
Regards

Zap proxy connection issue behind corporate proxy

I'm trying to use the zap proxy running on docker image. It works good on my local machine but when trying to use it behind corporate network the zap proxy requests timeout because it can't connect to the internet. I already have configured the http_proxy and https_proxy environmental variables but it seems that zap proxy isn't using them
You can configure a chained proxy (outbound proxy) for ZAP to use. Via Tools : Options > Connection (in the GUI), or the endpoints below in the API.
optionUseProxyChain
optionUseProxyChainAuth
optionProxyChainName
optionProxyChainPassword
optionProxyChainPort
optionProxyChainPrompt
optionProxyChainRealm
optionProxyChainSkipName
optionProxyChainUsername
proxyChainExcludeDomains

can not deploy web service via endpoint.publish() in apache reverse proxy env

we have a weblogic server in the internal network without SSL. To access the application, apache server is installed as a reverse proxy and also have configure SSL. it is ok to deploy web service via endpoint.publish(address) that address is get from httpservletrequest.getRequestURL() if the access url is internal. But failed and throw the below exception if the access url is proxy url. Any idea to publish it via proxy url?
weblogic.wsee.server.ServerURLNotFoundException: Cannot resolve URL for protocol http/https
at weblogic.wsee.server.ServerUtil.getHTTPServerURL(ServerUtil.java:211)
at weblogic.wsee.server.ServerUtil.getServerURL(ServerUtil.java:150)
at weblogic.wsee.server.ServerUtil.getServerURL(ServerUtil.java:137)
at weblogic.wsee.jaxws.spi.WLSEndpoint.calculatePublicAddressFromEndpointAddress(WLSEndpoint.java:335)
at weblogic.wsee.jaxws.spi.WLSEndpoint.publish(WLSEndpoint.java:207)
As per Oracle KM: Secure WebService call throwing CANNOT RESOLVE URL FOR PROTOCOL HTTP/HTTPS through web server(APACHE) plug-in. (Doc ID 1598617.1)
This is a Product Bug 8358398. For wls 10.3.0 to 10.3.2 you need to apply patch for this BUG and set -Dweblogic.wsee.useRequestHost=true
Blockquote
in your JAVA_OPTIONS.
For 10.3.3 and above version you need not to apply the patch. You can only set the above flag to true.

Deploying Maven artifact on Apache HTTP

I am new to web hosting.
I want to use an Apache HTTP server to host the site for my artifact built with Maven.
Since Maven uses protocols like SCP, what else should I require to configure the system?
How should I configure the system so that my artifact is available on my HTTP server?
I could set up Artifactory, but I want to know if it is possible to do so without any other third party artifact management system.
Thanks!