upgrade-04-05.txt 2.5 KB

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