[JIRA] (JENKINS-16345) CLI does not work through reverse proxy
Sidnei da Silva commented on JENKINS-16345 CLI does not work through reverse proxy I'm experiencing the same problem. Any information that could be provided to help diagnose? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16531) jenkins-cli with apache+ssl fails with 403
Sidnei da Silva created JENKINS-16531 jenkins-cli with apache+ssl fails with 403 Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: cli Created: 30/Jan/13 12:33 AM Description: Using jenkins-cli with public key authentication. jenkins-cli -s http://localhost:8080 help works. Using jenkins-cli with public key authentication. jenkins-cli -s https://jenkins.example.com help fails with a 403. Exception in thread "main" java.io.IOException: Server returned HTTP response code: 403 for URL: https://jenkins.example.com/cli at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1403) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254) at hudson.cli.FullDuplexHttpStream.init(FullDuplexHttpStream.java:61) at hudson.cli.CLI.init(CLI.java:110) at hudson.cli.CLI.init(CLI.java:82) at hudson.cli.CLI._main(CLI.java:250) at hudson.cli.CLI.main(CLI.java:199) Apache configuration is a simple vhost with ProxyPass/ProxyPassReverse at the root. Project: Jenkins Priority: Minor Reporter: Sidnei da Silva This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16531) jenkins-cli with apache+ssl fails with 403
Sidnei da Silva commented on JENKINS-16531 jenkins-cli with apache+ssl fails with 403 Apparently this might be related to SNI (or the lack thereof) on the client side. Since this host has multiple SSL vhosts with the same IP, the following config setting was added: SSLStrictSNIVHostCheck on ... which causes non-SNI clients to be rejected (http://httpd.apache.org/docs/2.2/mod/mod_ssl.html#sslstrictsnivhostcheck) Changing it to: SSLStrictSNIVHostCheck off ... gets rid of the 403. However the client instead will hang. Seems similar to JENKINS-11560 and JENKINS-16345, though the SNI problem could be considered a separate issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13600) Cannot access JNLP URL with apiToken after upgrade to 1.461
Sidnei da Silva created JENKINS-13600: - Summary: Cannot access JNLP URL with apiToken after upgrade to 1.461 Key: JENKINS-13600 URL: https://issues.jenkins-ci.org/browse/JENKINS-13600 Project: Jenkins Issue Type: Bug Components: core Reporter: Sidnei da Silva Accessing the JNLP URL on an OpenID-protected instance does not work anymore after upgrading to 1.461. Reverting to 1.459 makes it work again. Error with 1.461: Exception: Unexpected authentication type: org.acegisecurity.providers.UsernamePasswordAuthenticationToken@9f6d50cd: Username: hal; Password: [PROTECTED]; Authenticated: false; Details: org.acegisecurity.ui.WebAuthenticationDetails@957e: RemoteIpAddress: 127.0.0.1; SessionId: null; Not granted any authorities To test: curl -kinsecure -u user:apitoken https://localhost/computer/computer-name/slave-agent.jnlp -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13600) Cannot access JNLP URL with apiToken after upgrade to 1.461
[ https://issues.jenkins-ci.org/browse/JENKINS-13600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162052#comment-162052 ] Sidnei da Silva commented on JENKINS-13600: --- FWIW, sounds like a similar issue to JENKINS-11562, though I haven't tried to dig into the source yet. Cannot access JNLP URL with apiToken after upgrade to 1.461 --- Key: JENKINS-13600 URL: https://issues.jenkins-ci.org/browse/JENKINS-13600 Project: Jenkins Issue Type: Bug Components: core Reporter: Sidnei da Silva Accessing the JNLP URL on an OpenID-protected instance does not work anymore after upgrading to 1.461. Reverting to 1.459 makes it work again. Error with 1.461: Exception: Unexpected authentication type: org.acegisecurity.providers.UsernamePasswordAuthenticationToken@9f6d50cd: Username: hal; Password: [PROTECTED]; Authenticated: false; Details: org.acegisecurity.ui.WebAuthenticationDetails@957e: RemoteIpAddress: 127.0.0.1; SessionId: null; Not granted any authorities To test: curl -kinsecure -u user:apitoken https://localhost/computer/computer-name/slave-agent.jnlp -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
