upgrade-04-05.xml 2.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354
  1. <?xml version="1.0" encoding="ISO-8859-1"?>
  2. <document><properties><title>Acegi Security - Upgrading from version 0.4 to 0.5</title></properties><body><section name="Upgrading from 0.4 to 0.5"><p>The following should help most casual users of the project update their
  3. applications:
  4. <ul>
  5. <li>All filters are now loaded via FilterToBeanProxy. The FilterToBeanProxy
  6. obtains the filter from a Spring application context via the
  7. WebApplicationContextUtils.getApplicationContext() method. Refer to the
  8. reference documentation to see the new configuration of filters.</li>
  9. <li>SecurityEnforcementFilter now requires an AuthenticationEntryPoint
  10. and PortResolver. Refer to the reference documentation to see the
  11. alternatives AuthenticationEntryPoint implementations available. Simply
  12. use the PortResolverImpl for the PortResolver requirement.</li>
  13. <li>Any of your login or login failure pages that previously referred to
  14. AuthenticationProcessingFilter.ACEGI_SECURITY_LAST_EXCEPTION_KEY
  15. should now use
  16. net.sf.acegisecurity.ui.AbstractProcessingFilter.ACEGI_SECURITY_LAST_EXCEPTION_KEY.</li>
  17. <li>DaoAuthenticationProvider no longer provides setters for case sensitivity
  18. handling. The respective AuthenticationDao implementations should decide
  19. whether or not to return User instances reflecting the exact case of the
  20. requested username. The new PlaintextPasswordEncoder offers a setter for
  21. ignoring the password case (defaults to require exact case matches).</li>
  22. <li>DaoAuthenticationProvider now provides caching. Successful authentications
  23. return DaoAuthenticationTokens. You must set the mandatory "key" property
  24. on DaoAuthenticationProvider so these tokens can be validated. You may
  25. also wish to change the "refreshTokenInterval" property from the default
  26. of 60,000 milliseconds.</li>
  27. <li>If you're using container adapters, please refer to the reference
  28. documentation as additional JARs are now required in your container
  29. classloader.</li>
  30. <li>Whilst not really a change needed to your program, if you're using
  31. Acegi Security please consider joining the acegisecurity-developer mailing
  32. list. This is currently the best way to keep informed about the project's
  33. status and provide feedback in design discussions. You can join at
  34. https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer.
  35. Please continue using the Spring Users mailing list for general support.</li>
  36. </ul>
  37. </p><p>
  38. There are also lots of new features you might wish to consider for your
  39. projects. These include CAS integration, pluggable password encoders
  40. (such as MD5 and SHA), along with pluggable salt sources. We hope you find
  41. the new features useful in your projects.
  42. </p></section></body></document>