How to access RSS/CC.XML from secured Jenkins

[Kasper Garnaes]

We currently have a Jenkins server which is secured using Jenkins' own
user database.

We would like to use some of the tools available for monitoring the
status of our builds like CCMenu (http://ccmenu.sourceforge.net/),
Hudson Notifier (http://code.google.com/p/hudson-on-cocoa/) etc.

Most of the tools work by entering the URL of either rssAll feed or
cc.xml feed. However since Jenkins is secured access to these
resources require authentication.

According to the wiki (https://wiki.jenkins-ci.org/display/JENKINS/
Authenticating+scripted+clients) these resources should be accessible
using HTTP BASIC authentication. However accessing these resources
using classic http://username:password@host/jenkins does not seem to
work when using these tools or testing in a browser. A HTTP 403
response code is returned and browsers are redirected. In CURL such an
url works fine.

Has anyone else experienced this and/or is there any way to make such
urls work ubiquitously?

Thanks in advance!

[Didier Durand]

Hi,

Yes, I add this problem of 403 when trying to remotely launch builds,
I solved it inspiring mysekf from this code samples:
http://hc.apache.org/httpcomponents-client-ga/tutorial/html/authentication.html

The jenkins login process is detailled here:
http://jenkins.361315.n4.nabble.com/Remote-API-authentication-not-working-td369554.html#a369554

By combining those 2, you should be able to fix your code.

regards

didier

On Aug 11, 9:21 pm, Kasper Garnaes <kasper.garn...@gmail.com> wrote:
> We currently have a Jenkins server which is secured using Jenkins' own
> user database.
>
> We would like to use some of the tools available for monitoring the
> status of our builds like CCMenu (http://ccmenu.sourceforge.net/),
> Hudson Notifier (http://code.google.com/p/hudson-on-cocoa/) etc.
>
> Most of the tools work by entering the URL of either rssAll feed or
> cc.xml feed. However since Jenkins is secured access to these
> resources require authentication.
>
> According to the wiki (https://wiki.jenkins-ci.org/display/JENKINS/
> Authenticating+scripted+clients) these resources should be accessible
> using HTTP BASIC authentication. However accessing these resources

> using classichttp://username:password@host/jenkinsdoes not seem to