-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Minor
-
Component/s: saml-plugin
-
Environment:Jenkins LTS 2.121.x
saml:1.0.7
-
saml-1.1.0
1
Using a fake proxy like 999.999.999.999:8080 for Running Jenkins Behind a Proxy Configuration, and then testing a URL (https://federation.basf.com/nidp/saml2/metadata) and results are expected, the URL is not reachable.
2
What is not expected is that for SAML plugin configuration > Idp Metadata Test URL, it succeeded to connect. As result, we can determinate that the saml plugin is skipping the proxy configuration.
3
As a workaround, I tried to configuring proxy by JVM paarmeters but I got the same results as point 2, meaning that with the fake proxy the Test connection is sucessfull
$> ps aux | grep jenkins carlosrodlop 1294 0.0 0.0 2434840 772 s002 S+ 1:33PM 0:00.00 grep --color=auto jenkins carlosrodlop 1217 0.0 10.1 9777568 1694448 s001 S+ 1:31PM 0:46.00 /usr/bin/java -Djenkins.model.Jenkins.slaveAgentPort=21942 -Djenkins.install.runSetupWizard=false -Djenkins.model.Jenkins.logStartupPerformance=true -Dhudson.TcpSlaveAgentListener.hostName=oss.example.crl -Dhttp.proxyHost=999.999.999.999 -Dhttp.proxyPort=8080 -Djava.security.egd=file:/dev/./urandom -Xdebug -Xrunjdwp:transport=dt_socket,suspend=n,server=y,address=0.0.0.0:8194 -XX:MaxPermSize=512m -Xms256m -Dhudson.DNSMultiCast.disabled=true -jar /Users/carlosrodlop/Support/labs/jenkins-home-oss/jenkins.war --httpPort=8184 --httpListenAddress=0.0.0.0 carlosrodlop 1064 0.0 0.0 2463080 1388 s001 S+ 1:31PM 0:00.03 /bin/bash /Users/carlosrodlop/code/github/carlosrodlop/support-shinobi-tools/bin/cbsupport-jenkins oss 2.138.1
- links to
