On 8/30/13, Matevž Bradač <[email protected]> wrote: > On 29. Aug, 2013, at 17:45, Olemis Lang wrote: > [...] >> >> So I guess I've gathered the following alternatives so far : >> >> 1. add an option to tracd to supply a regex for auth match >> 2. similar to (1) but without a regex , just exclude /login >> 3. similar to (2) but without exposing the option as a tracd arg >> * which reminds me the previous patch suggested for >> BH installer script >> 4. install HttpAuthPlugin , configure it prior to the test run, ... >> 5. write an AccountManagerPlugin extension to enforce HTTP >> digest auth on /login/.* >> 6. same as (5) but also supporting configurable regex >> >> What would you recommend ? I think I'd choose (1) , (2) or (3) because >> all others require yet another dependency in Bloodhound RPC plugin >> just to run the test suite . Needless to mention that RPC behind tracd >> will not be possible ootb, but that's another subject. > > I think I'd vote for (1) or (3), the (2) seems too limiting for general > use.
Yes , I guess I quite agree with you > Having a configurable regex or list of "exclude" paths makes more sense, > especially if it's backported to trac (which IMO would be a good idea). > I'm in favor of adding such feature in Trac + Bloodhound , see http://trac.edgewall.org/ticket/11287 In the end I made use of skiplogin arg in BH functional testers (... which I did not remember ...) so as to run Bloodhound RPC test suite by supplying --auth option in to tracd , thus avoiding interactions with login form . Nevertheless in the not-so-long term I think it will be necessary to combine browser + RPC access and such 'option' will be necessary . -- Regards, Olemis - @olemislc
