Re: Wicket + security, what are the best options? Spring Security reached almost all the way...

[Jimi <ji...@mogul.com>]

Thanks for the link. I've already looked at that page and besides the fact
that alot of the xml/code is missing in the beginning (like web.xml) I was
shocked by the amount of boilerplate code needed to get the wicket side
working.

That tells me that either 
1) people actually copy-paste all this boilerplate code and maybe do minor
modifications for their project
2) people use this code as a guide, and write a lot of the implementation
them selfs
3) there is some easier (but undocumented) way to use wicket auth-roles (or
WASP/SWARM or wicket-shiro), with way less boilerplate code needed. Maybe .
4) people use some other framework

1 and 2 seems just plain wrong, the way I see it. If 3 or 4 is the case I
would love to hear about it from someone.

/Jimi

> You can use Spring security with wicket auth-roles, I works out pretty
> nice
> compared to the alternatives.  iirc You need do your normal Spring
> setup, extend AuthenticatedWicketApplication, and AuthenticatedSession
>  which has an authenticate method you'll call your UserDetails bean from.
> 
> Outdated Link
> https://cwiki.apache.org/WICKET/spring-security-and-wicket-auth-roles.html#SpringSecurityandWicket-auth-roles-ExampleWicket1.3.5

-- 
View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-security-what-are-the-best-options-Spring-Security-reached-almost-all-the-way-tp2068415p2068908.html
Sent from the Wicket - User mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org