Hi, Anyone tried integrating Wicket with JSecurity ?
http://www.jsecurity.org/ Maarten On Thu, Sep 25, 2008 at 4:54 PM, James Carman <[EMAIL PROTECTED]> wrote: > You can bridge the gap between Spring Security's default URL-based > model and the component-based model in Wicket. That's what we do here > at work. If you want an example, let me know. I've got one out there > on my public example stuff somewhere. You could try poking around in > (I think it's there): > > http://svn.carmanconsulting.com/public/wicket-advanced/trunk > > > On Thu, Sep 25, 2008 at 10:51 AM, Claus Myglegaard Vagner > <[EMAIL PROTECTED]> wrote: >> Hi, >> >> I'm about to start a new project using Wicket and is currently examining >> which security framework to apply for. I'm looking for best practices >> implementing security to a Wicket application. >> >> Wicket has WASP which Swarm is an implementation of and then there is >> wicket-auth-roles. Is wicket-auth-roles related to WASP in any way or is >> it a completely different security platform for wicket? >> >> Which security framework will be the future for wicket? >> >> I am thinking on using Spring Security (prior Acegi) for securing the >> service layer through aspects. Spring Security has build in authentication >> integration with various technologies like LDAP and for example a >> "remember me" function. I'm thinking that this project should benefit from >> this built in functionality, but maybe the wicket frameworks has some of >> the same possibilities? >> >> Well, should I integrate Spring Security to Swarm or wicket-auth-roles and >> what would that give me? I know that Spring Security is url based and >> Swarm is component based, but not sure yet that I need to specify security >> on the component level. >> >> Regards Claus >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
