Guys,

did anyone use Spring Security <intercept-url> for managing authorization
for Wicket-driven webapp?

It's still unclear to me: can I use SS 3 as an authorization tool with
configuration like:

<security:http create-session="never" auto-config="true">
   <security:intercept-url pattern="/admin" access="ROLE_ADMIN"/>
   <security:intercept-url pattern="/**"/>
</security:http>

or there is no way to omit wicket-auth-roles?

P.S. Although Wicket 'auth' annotations work, I couldn't make it work with
Spring Security only.

Thanks,
Dmytro.

Reply via email to