From: Rutger V. <rut...@gm...> - 2010-01-04 13:11:56
|
Sounds good to me. The commented-out line: <!-- property name="passwordEncoder" ref="passwordEncoder"/ --> suggests to me that the daoAuthenticationProvider bean needs to be passed a passwordEncoder bean (presumably implementing a passwordEncoder interface?) which consequently needs to be defined somehow. Does acegi supply us with one for free? On Sat, Dec 26, 2009 at 9:28 PM, Hilmar Lapp <hl...@ne...> wrote: > > On Dec 26, 2009, at 1:41 PM, Vladimir Gapeyev wrote: > > My plan now would be to learn acegi (which, btw, is SpringSecurity starting > with Spring 2.0, which TB2 uses) and what it offers for password hashing -- > unless someone offers more focused guidance on what I should do. > > I'll follow the suggestions at http://acegisecurity.org/suggested.html > > That sounds like a good plan to me. If this can be solved declaratively, all > the better. > -hilmar > -- > =========================================================== > : Hilmar Lapp -:- Durham, NC -:- informatics.nescent.org : > =========================================================== > > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Treebase-devel mailing list > Tre...@li... > https://lists.sourceforge.net/lists/listinfo/treebase-devel > > -- Dr. Rutger A. Vos School of Biological Sciences Philip Lyle Building, Level 4 University of Reading Reading RG6 6BX United Kingdom Tel: +44 (0) 118 378 7535 http://www.nexml.org http://rutgervos.blogspot.com |