Connection error for OpenSSL remote watch

[Laura Czajkowski]

Bug #579081 contains a remote watch, which has a unknown status and importance. The remote report shows that it is resolved.

When I opened the remote watch settings, it shows 'Launchpad couldn't connect to OpenSSL RT.' in an error box. The remove tracker is online.

So, I suppose the OpenSSL remote bugwatch is broken...

Greetings,

[Lucy Llewellyn (lucyllewy)]

also the RT is failing to respond on bug #654493. It seems the Openssl RT is behind an authentication block which for most issues can be sidestepped by using the username and password both of "guest". http://openssl.org/support/rt.html gives details of how to include a username and password parameter in the URL request, which I've duplicated below:

"The OpenSSL project has set up a request tracker at http://rt.openssl.org/ offering read-only access using the account guest with the password guest. The username and password can also be specified in the URL for example: http://rt.openssl.org/?user=guest&pass=guest. A link to a specific bug can be created using for example: http://rt.openssl.org/Ticket/Display.html?user=guest&pass=guest&id=1"

id is the bug number, user and pass are both set to guest, the rest should be as already set in launchpad's code somewhere on the backend.

[Lucy Llewellyn (lucyllewy)]

it seems my previous comment may not be helpful. Looking through the code for LaunchPad's RT connector suggests that it will try guest:guest when it can't get any credentials from the database[1]

I would imagine that this might be fixed by a simple data tweak of the OpenSSL RT configuration by someone who has access to LP's administration interface and/or database.

[1] http://bazaar.launchpad.net/~launchpad-pqm/launchpad/devel/view/head:/lib/lp/bugs/externalbugtracker/rt.py#L54