I have made some further debugging and i have found that the NTLM filter performs a getSession which creates a HttpSession and further in the call stack performs a LoginContext.login and call the JAAS Nuxeo JBossLoginModule which generates the exception.
Now i am trying to use JAASLounge project which now offers a JAAS NtlmLoginModule to replace the NTLM filter. I am trying to replace the JBossLoginModule by this one just to see what's happening... "Frédéric Thise" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] >I know, i did check the generated web.xml; after moving the marker in the >template web.xml file, the only filters before mine are the SimpleCache >filters... > As you can see in the stack trace, the seam lifecycle is executed prior to > the filters. It initialize several nuxeo components and i guess one of > them generates the ClientException (connection refused)... > > I have removed from the template web.xml (and thus in the generated > web.xml file) the <login-config> part, i assumed that the first displayed > page would be the one normally shown directly after the normal login page > (when the default <login-config> was in place). Is it correct or should i > add something to "branch" to this page (In this case the Workspace, > Section,... selection screen) ? > > I just try to figure out if the problem is there because the seam > components are initialized (and generates an exception) before the NTLM > filter is executed or if it is just the fact that after performing the > NTLM authentication, no branch is made to the default page... I am new to > JSF/Facelets and i had little time to get familiar with it so my question > might seem a bit silly... > > Any insight would be appreciated ;) > > "Tiry" <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] > Le mardi 27 mars 2007 à 11:25 +0200, Frédéric Thise a écrit : >> 192.168.3.34 is my local machine which is running both my test JBoss >> server >> and my browser. >> >> i tried to patch the web.xml template file to put the marker >> FILTER-MAPPING >> on top of the filter-mappings "hardcoded" in the file but nothing >> changed. > You can easily check that by looking at the deployed web.xml, it will > show you what filters are declared before yours. > >> Before the NTMLHttpFilter gets the chance to do the work, Nuxeo performs >> some work... Is it possible that this work is initiated by a listener or >> something that takes precedence to >> the filters? > It depends on the filters that are before yours. > Nuxeo webapp itself has no filter that access ejb. > > If you want, you can safely remove FancyURLFilter by editing > org.nuxeo.ecm.platform.ui.web/src/org/nuxeo/ecm/platform/ui/web/rest/FancyURLConfig.java > and setting all boolean values to false (there will be an EP very soon > for that). > > But during session startup, there may be seam componnents that are > automatically started. > > If you breakpoint inside your filter, you should be able to see : > - if there is already an error when the filter is called > - what code generated the error > > > Tiry > >> >> >> >> "Tiry" <[EMAIL PROTECTED]> wrote in >> message >> news:[EMAIL PROTECTED] >> Le mardi 27 mars 2007 10:34 +0200, Frdric Thise a crit : >> > Did anyone manage to integrate Nuxeo with NTLM ? >> I guess that nobody tried before you. >> >> > 192.168.3.34 >> What is 192.168.3.34, your local JBoss server ? >> >> Are you sure your filter is on top of the filter stack ? Otherwise, you >> will have ejb (then JNDI) calls before beeing authenticated. >> >> > i have also tried the BASIC authentication method in web.xml but in >> this case i always have the login dialog popping in my browser... Even >> if i use IE on local intranet... >> >> Sounds perfectly normal to me, this is the standard Tomcat behavior. >> >> >> >> _______________________________________________ >> ECM mailing list >> [email protected] >> http://lists.nuxeo.com/mailman/listinfo/ecm >> _______________________________________________ ECM mailing list [email protected] http://lists.nuxeo.com/mailman/listinfo/ecm
