I recently had similar a problem. First thing, turn up the trac logging verbosity so you can see how Mylyn is actually directing requests at the server.
Second, check your plugins. There are some known but poorly explained caveats when using the TracAccountManager and TracHttpAuth plugins. I couldn't really figure it out and as a last resort took a brute force approach... stripped out all plugins and re-created the python virtualenv. It worked in the end. For what it's worth, I now have Mylyn configured with the `Server:` field set to the base url (e.g. no /xml-rpc or anything of the other variations). And in my config: [httpauth] > formats = text/plain, text/xml, rss > paths = /xmlrpc, /login/xmlrpc, /rpc, /login/xmlrpc > Hopefully this gives you a steer in the right direction. Dwight -- Dwight Gunning Amsterdam, The Netherlands. +31 (0)6 2363 8344 | Twitter/Skype: dwightgunning [email protected] | http://dwightgunning.com On 8 August 2011 21:49, osimons <[email protected]> wrote: > > > On Aug 8, 6:27 pm, iapazmino <[email protected]> wrote: > > I'm trying to connect from an eclise mylyn connector to my trac project > > which is in htt://some-ip:8000/proj-env, but it returns an HHTP 302 error > > I suppose you mean http://...? > > > The configuration sets only the url and acces type to xml-rpc. It's an > > authenticated user and has the XML_RPC permission > > > > I've tried suffixing the url with /rpc and /login/rpc but none solves the > > problem. > > If you want to be authenticated, you need to use /login/rpc to make > sure credentials are requested. > > > Maybe I need something else to configure in the project environment? > > That is the question, and the really helpful answer is that "it > depends"... A few questions back to you: > > 1) When browsing the Trac and performing regular browser login, do you > enter your username/password in a form or via a browser prompt? > > 2) In a fresh browser, does the /login/rpc URL present you with a > browser prompt (ie. not a web form). > > 3) If not, how about using /login/xmlrpc URL? Does that present a > login prompt? > > RPC does not really care about how login is performed, that is really > an issue with the clients (like the java code used by your Mylyn > stack). Clients typically only support lowest common denominator for > authentication, and all that I have encountered supports basic > authentication. A few may support digest authentication, but they are > more exceptions. So, your server need to enforce basic authentication > at /login/rpc either by using server-based basic authentication or by > adding http://trac-hacks.org/wiki/HttpAuthPlugin and configure it to > intercept and authenticate the particular url and checking it against > your account-manager authentication (forms). > > > :::simon > > https://www.coderesort.com > http://trac-hacks.org/wiki/osimons > > -- > You received this message because you are subscribed to the Google Groups > "Trac Users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/trac-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
