Hi Eirik, Thanks for the time you've spent looking into my problem, it's much appreciated.
> I first thought you wanted the following: > > ,-------- ldap auth -- < trac > user <- (xml theme proxy ) < > '-------- cms website Exactly what I want. > 3: An url starting with /trac: > 1: should be served from the trac instance > 2: should be authenticated via ldap Should be served from the trac instance, *VIA* the xml theme proxy. > However, as far as I can tell collective.xdv is just a post-hook for > plone ? No, it sits in front of Trac too. (In fact it can sit in front of any website, which is where it's potential power comes from). But this is where my trouble begins. As soon as collective.xdv is in front of Trac, the authentication system fails. I'm not sure if collective.xdv is stripping authentication headers, or if there is a better way of Apache controlling the route of the authentication requests. > Should be as easy as: Your included configuration works great, if I don't want Trac themed by the collective.xdv proxy but have it appear on the same address, but as detailed above, this isn't my end goal (although it might have to be Plan B) > I would suggest not > cramming everything into one apache config instance, but rather set > everything up as if you were setting up seperate servers. Good advice :) Jon. -- 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.
