negotiateSecurityFilterEntryPoint refresh, re-authenticate user ?

Oct 14, 2010 at 6:45 AM
Edited Oct 14, 2010 at 6:47 AM

i did my testing   


1. with ntlm-jciffs spring default ntlm ,  after login into my application, i press "refresh",  user will not required to re-authenticate again


2. i use waffle negotiatesecurityfilterentrypoint,  after login to my application, on any page, as long as i press "refresh", i can see user is re-authenticate, not matter, i choose to use "ntlm" or "negotiate" as protocol


any idea, how to troubleshoot/solve this problem? is it because of below   <security:custom-filter  before="AUTHENTICATION_PROCESSING_FILTER" />



my appcontext.xml like below


 <security:http entry-point-ref="negotiateSecurityFilterEntryPoint" auto-config="false">


  <security:intercept-url pattern="/cannotlogin.jsp" filters="none" />
        <security:intercept-url pattern="/**" access="ROLE_USER"  />
<security:intercept-url pattern="/*.jsp" filters="none" />
<security:intercept-url pattern="/css/**" filters="none"/>
<security:intercept-url pattern="/images/**" filters="none"/>
<security:intercept-url pattern="/js/**" filters="none"/>
<security:intercept-url pattern="/development-bundle/**" filters="none"/>
<security:intercept-url pattern="/login.jsp**" filters="none"/>
<security:intercept-url pattern="/error.jsp**" filters="none"/>
<security:form-login login-page="/login.jsp" authentication-failure-url="/login.jsp?error=auth" />

<security:concurrent-session-control max-sessions="1" />



 <bean id="negotiateSecurityFilterEntryPoint" class="waffle.spring.NegotiateSecurityFilterEntryPoint">
   <property name="provider" ref="waffleSecurityFilterProviderCollection" />



    <bean id="waffleNegotiateSecurityFilter" class="waffle.spring.NegotiateSecurityFilter">
        <security:custom-filter  before="AUTHENTICATION_PROCESSING_FILTER" />
        <property name="provider" ref="waffleSecurityFilterProviderCollection" />

Oct 14, 2010 at 7:21 AM

another test, i found it happen in internet explorer, and work ok with firefox.

Oct 14, 2010 at 8:01 AM

sorry my mistake. because of my javascript onunload that cause the problem.