And it is demonstrated here:
http://jumpstart.doublenegative.com.au/jumpstart/examples/infrastructure/protectingpages
Geoff
On 19/05/2010, at 5:03 AM, Nicolas Bouillon wrote:
Le 18/05/2010 20:55, Thiago H. de Paula Figueiredo a écrit :
On Tue, 18 May 2010 15:20:58 -0300, Nicolas
I've looked around the TSS 2.1 source code, and it seems that a
ComponentRequestFilter already exists :
http://www.localhost.nu/svn/public/tapestry-spring-security/branches/2.1/src/main/java/nu/localhost/tapestry5/springsecurity/services/internal/T5ComponentRequestFilter.java
It is correctly
Oups, it seems i've made many people lost their time :
The T5ComponentRequestFilter is not present in TSS 2.1, and i've checkout
the branch (the 2.1.1-SNAPSHOT).
I just compiled it and it works fine.
After all, it is a good news !
Regards.
Nicolas.
On Wed, 19 May 2010 13:25:24 +0200, Nicolas
Le 17/05/2010 18:40, Thiago H. de Paula Figueiredo a écrit :
On Mon, 17 May 2010 11:12:48 -0300, Nicolas Bouillon
nico...@bouil.org wrote:
Hi,
Hi!
I'm using Tapestry 5.1 with Tapestry Spring Security 2.1.0 and I've
noticied a strange behaviour :
But even if the user is not logged in, the
On Tue, 18 May 2010 15:00:20 -0300, Nicolas Bouillon nico...@bouil.org
wrote:
I'm afraid it is also a no-go for using TSS with this kind of security
hole. What a deception because it is easiest than a spring security XML
file.
On the other hand, it's easy to create a
Le 18/05/2010 20:06, Thiago H. de Paula Figueiredo a écrit :
On Tue, 18 May 2010 15:00:20 -0300, Nicolas Bouillon
nico...@bouil.org wrote:
I'm afraid it is also a no-go for using TSS with this kind of
security hole. What a deception because it is easiest than a spring
security XML file.
On
+ TSS 2.1.0] @Secured annotation on class doesn't avoid call
to onActivate
On Mon, 17 May 2010 13:48:57 -0300, Alex Kotchnev akoch...@gmail.com
wrote:
Thiago,
what would be the proper render event to decorate for access security
checks (if not @SetupRender) if the page is annotated
On Tue, 18 May 2010 15:21:43 -0300, Jim O'Callaghan
jc1000...@yahoo.co.uk wrote:
This is really worrying. Is it possible to contribute / decorate a
ComponentEventRenderFilter to overcome this security hole?
Just write a ComponentEventRenderFilter with the checking logic and
contribute
On Tue, 18 May 2010 15:20:58 -0300, Nicolas Bouillon nico...@bouil.org
wrote:
I guess you mean ComponentEventRequestFilter, like this kind of stuf :
Yes, I made a typo in the
Le 18/05/2010 20:55, Thiago H. de Paula Figueiredo a écrit :
On Tue, 18 May 2010 15:20:58 -0300, Nicolas Bouillon
nico...@bouil.org wrote:
I guess you mean ComponentEventRequestFilter, like this kind of stuf :
Yes, I made a typo in the
Hi,
I'm using Tapestry 5.1 with Tapestry Spring Security 2.1.0 and I've
noticied a strange behaviour :
I've annoted my class to require the user to be logged :
@org.springframework.security.annotation.Secured(ROLE_USER)
public class TestPage {
@Inject
private Logger log;
public
On Mon, 17 May 2010 11:12:48 -0300, Nicolas Bouillon nico...@bouil.org
wrote:
Hi,
Hi!
I'm using Tapestry 5.1 with Tapestry Spring Security 2.1.0 and I've
noticied a strange behaviour :
But even if the user is not logged in, the onActivate is called.
As far as I can remember, TSS checks
Thiago,
what would be the proper render event to decorate for access security
checks (if not @SetupRender) if the page is annotated as @Secured ?
Nicolas,
although it certainly is annoying, can you annotate the page w/ @Secured,
and in the cases where you have onActivate, annotate them as
On Mon, 17 May 2010 13:48:57 -0300, Alex Kotchnev akoch...@gmail.com
wrote:
Thiago,
what would be the proper render event to decorate for access security
checks (if not @SetupRender) if the page is annotated as @Secured ?
In this case, there's no rendering event that is triggered in
14 matches
Mail list logo
