On 31 July 2013 09:35, van Dalen, Andre <[email protected]> wrote: >> https://issues.apache.org/bugzilla/show_bug.cgi?id=53480 > >> --- Comment #20 from Sebb <[email protected]> --- If the settings really have >> to be provided via System properties, why do we need an AuthManager entry? >> Maybe the user > should just edit system.properties. > > As far as I'm concerned the complete configuration for a test should be > inside the testplan (as far as possible). > Editting system.properties between tests is error prone imho, adding these to > the AuthManager (or a separate KerberosManager) would be ideal.
However, what happens when the user provides two AuthManagers with different settings? That would be very easy to do by mistake. It feels wrong to set System properties, but perhaps it's the only option. Is there a better Kerberos implementation that is more suited to multi-threaded use?
