Community
Participate
Working Groups
Build ID: I20070625-1500 Steps To Reproduce: 1. Create a new XPlanner repository 2. Enter the username and password 3. Enable the http authentication and enter the username and password (this may be different from the username/password above) 4. Click Validate settings. The message 'The supplied credentials are invalid: Invalid user name or password.' appears. More information: The error log doesn't show any message regarding this error.
Seems pretty important, and is blocking a few people
Helen: The Trac connector is probably the simplest example to walk through how the Tasks framework sets up http connections and authentication.
The XPlanner SOAP implementation looks very much like the one for JIRA. I am not sure if the HTTP authentication was ever tested (there is no JUnit test case). Helen, I'll add a test case for JIRA and comment here if I can get it to work.
Steffen, thank you very much for checking this -- I am sure you will see more familiar pieces in the XPlanner connector, since it was really based on the Jira connector originally :-) -- it really helped to be able to see actual working code and use that as a starting point for our implementation.
I have tested basic HTTP authentication with JIRA and it seems to work fine.
Created attachment 75695 [details] updated client-config.wsdd to use custom httpsender class to pass http user/password This patch will allow http/proxy configurations to work with XPlanner, as long as the extra username/password are the same as the basic XPlanner username/password. Debugging the XPlanner code, it looks like it uses the http credentials as the XPlanner search credentials to find an existing defined Person. Still trying to figure out how to make different http username/password work.
Created attachment 75696 [details] mylyn/context/zip
It's me or the patch attach is empty ? I can't apply it, it shows just the description and nothing else. Why don't you commit the changes to cvs instead ?
All the patch contained were changes to client-config.wsdd -- not sure why those changes didn't get in. Will try again. I cannot check in because I don't have the rights yet -- gotta fix a few more bugs :-). Thanks for the heads up -Helen
Created attachment 75776 [details] second attempt
Ok, hopefully the second patch should work -- I think the problem was I didn't turn on the "patch" check box in the attachment dialog. Sorry. -Helen
As far as I can tell from XPlanner information, the same http and regular credentials being a requirement is the design. I will close this bug as fixed, and if I find out any info that indicates differently, will reopen.
<patch> Looks like this patch hasn't been applied yet, so reopening bug. Mik or Robert, it looks like I assumed it was checked in, and closed the bug prematurely, which probably dropped this out of your queries for patches to check in... Sorry.
Yes, somehow we missed it. Patch is now applied, ip log updated. Leaving for you to mark resolved as appropriate.
Thanks, Robert. I am now "refixing" the bug.
Fixing assignment.
Resolved.
