well maybe it does (surely since that's the LoginContext behavior) but error is not obvious at all.
I didn't got time to dig deeper into it but i think you are right and the main issue is the error message which should be more explicit saying configFile was not set and system property is missing or wrong. wdyt? PS: i changed of JVM version too, maybe LoginContext was modified, i didn't check this neither. *Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/8/7 Mark Thomas <ma...@apache.org> > On 06/08/2013 08:51, Romain Manni-Bucau wrote: > > Hi > > > > it seems we can now configure jaasrealm to use a jaas config file from > the > > webapp. That's great but it would need to fallback to old behavior (jaas > > system property to find its location) by default otherwise apps using an > > older tomcat are broken. > > > > wdyt? > > What makes you think it doesn't fall-back to the old behaviour if no > webapp specific file is specified? > > Here is the commit: > http://svn.apache.org/viewvc?view=revision&revision=1498498 > > Mark > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > >
