java - Spring Security: sudden classpath and Thymeleaf related issues after modifying the filter chain -


i'm trying integrate waffle-spring-security4 existing spring boot project, of configuration happens automatically. i've noticed when negotiatesecurityfilter in chain, weird things occur: classnotfoundexception on initializing trivial class 1 string property; thymeleaf template loaded fine can't resolved , on. when happened, had following filters in chain:

  1. webasyncmanagerintegrationfilter
  2. securitycontextpersistencefilter
  3. headerwriterfilter
  4. csrffilter
  5. logoutfilter
  6. negotiatesecurityfilter (by waffle)
  7. basicauthenticationfilter
  8. requestcacheawarefilter
  9. securitycontextholderawarerequestfilter
  10. sessionmanagementfilter
  11. exceptiontranslationfilter
  12. filtersecurityinterceptor

with switching http basic authentication issue disappears, think issue might filters above. have idea on how troubleshoot this? (if have strategy debugging similar issues, excellent.)

yes, caused waffle, has turned out.

the problem once you've done successful authentication waffle, rest of run, necessary files not accessible. caused trying load classpath fail miserably. have add here i've tried run source gradle bootrun , building jar , running instead; in first case, thymeleaf resolution failed, in second, spring class not found.

it turns out if remote user (who's logging in via sso) doesn't have read access files, once user it's authenticated, application won't work anymore @ all! wasn't aware of environmental change caused waffle, don't recall seeing on docs - makes sense. after gave read access user, started work.


Comments

Popular posts from this blog

javascript - Slick Slider width recalculation -

jsf - PrimeFaces Datatable - What is f:facet actually doing? -

angular2 services - Angular 2 RC 4 Http post not firing -