Error with SSL/Authentication

[atle@…]

When Hudson is running on https and with HTTP Authentication...

The parsing of details will fail because of the request for the /api/json details will just contain the 401 error, not a valid json object.

Even when the RSS url is on basic http, it uses the links in the rss feed to get the details, and they contain in my case the https links

[roadrunner]

For the feed you should be able to include the username and password in the feed_url (i.e. https://user:pass@.../). But yes, for the details this won't work.

Ok, I'm attaching a patched version the plugin which adds username and password options and passes those to all urls (the username/password need not be embedded in the feed url). Please try it out and let me know (I've only tested to the point that it doesn't seem to break anything).

[roadrunner]

Patched plugin to support authentication

[anonymous]

Can anyone update if this issue has been fixed?

[roadrunner]

If someone could confirm that the attached version actually works on a password-protected hudson instance I will check in the fix and close the ticket.

[roadrunner]

(In [5698]) Added support for configuring hudson authentication info. This closes #4113.

[roadrunner]

(In [6100]) Fixed authentication handling. There were two issues:

1. need to register the auth info for all paths not just the feed, because the descriptions will have different paths
2. feedparser's authentication handling is broken (there's an over two year old bug report on it at ​http://code.google.com/p/feedparser/issues/detail?id=40 but the fix there is not correct). So we just open the url ourselves which avoids feedparser's handler and hence the problem.

This really fixes #4113 and hopefully addresses #5430.