> Why don't you use annotations for that? Something like @PublicPage? If the
> page hasn't it, it is protected.
>
> Unless there are pages that need some internal logic to decide if they're
> public or protected (hence an interface with a isPublic() method),
> annotations are a better solution for
Beirut, Bucharest,
Istanbul
Subject: Re: Authentification in Tapestry
On Thu, Jun 4, 2009 at 3:41 AM, Thiago H. de Paula Figueiredo
wrote:
> Em Wed, 03 Jun 2009 22:07:28 -0300, Onno Scheffers
> escreveu:
>
>> I'm also using a custom dispatcher.
>> The thing I don'
On Thu, Jun 4, 2009 at 3:41 AM, Thiago H. de Paula Figueiredo
wrote:
> Em Wed, 03 Jun 2009 22:07:28 -0300, Onno Scheffers
> escreveu:
>
>> I'm also using a custom dispatcher.
>> The thing I don't like about most of the current examples/solutions I've
>> seen so far is that access is allowed by d
On Wed, Jun 3, 2009 at 9:13 PM, Thibaut Gadiolet
wrote:
> OK, I stop using a full T5 solution to handle authentication/authorization.
> I am using ACEGI with a basic configuration, you can easily integrate it to
> your T5 projects, It's not as heavy as I thought, and it turned out to be
> very e
That's the way I've written the access control on our system.
-Original Message-
From: Christian Senk [mailto:senk.christ...@googlemail.com]
Sent: 03 June 2009 20:24
To: Tapestry users
Subject: Re: Authentification in Tapestry
We are using a custom dispatc
Em Wed, 03 Jun 2009 22:07:28 -0300, Onno Scheffers
escreveu:
I'm also using a custom dispatcher.
The thing I don't like about most of the current examples/solutions I've
seen so far is that access is allowed by default if the developer
forgets to
add a specific annotation. I'd like the pag
>
> All you have to do is to annotate the desired page with
> "@Secured(Role.ADMIN)"
I'm also using a custom dispatcher.
The thing I don't like about most of the current examples/solutions I've
seen so far is that access is allowed by default if the developer forgets to
add a specific annotation
Thank you guys,
I like the idea of implementing my own dispatcher.
BTW, Thiago, ACEGI is what I am using, as I said at the top of this
conversation.
I think it is still the best way to solve Authentication/authorization
issues with Tapestry... but it's always interesting to see if a full T5
solut
We have build our own using a custom RequestFilter which is not
dissimilar to Christians Dispatcher approach.
Cheers,
Joost
PS: I love the simple way to also check for ajax requests to secure
pages and forward to the login if needed:
PrintWriter writer = response.getPrintWriter("application/json
Em Wed, 03 Jun 2009 16:13:18 -0300, Thibaut Gadiolet
escreveu:
OK, I stop using a full T5 solution to handle
authentication/authorization.
I am using ACEGI with a basic configuration, you can easily integrate it
to your T5 projects, It's not as heavy as I thought, and it turned out
to b
We are using a custom dispatcher called "AccessControlDispatcher".
It is like the AccessDispatcher described in the howto-wiki, but in addition
it checks for certain roles.
This works through a SessionState object that implements an interface used
by the dispatcher to determine if the SessionStat
OK, I stop using a full T5 solution to handle authentication/authorization.
I am using ACEGI with a basic configuration, you can easily integrate it to
your T5 projects, It's not as heavy as I thought, and it turned out to be
very efficient.
But if someone gets a better solution full T5, I'm open
Thanks for tips, Thiago!
> This has been discussed in this list before. Check the archives
> (http://www.nabble.com/Tapestry---User-f340.html) for some ideas.
> Usually they are centered around a RequestFilter or a
> ComponentClassTransformer.
>
---
On Thu, May 21, 2009 at 6:01 PM, Thiago H. de Paula Figueiredo
wrote:
>> I am creating a web application using Tapestry for the GSoC.
>> I was wondering what is best way to fit security requirements of a mere
>> application (login/password/roles).
>
> This has been discussed in this list before.
On Thu, May 21, 2009 at 12:50 PM, Thibaut Gadiolet
wrote:
> Hi,
Hi!
> I am creating a web application using Tapestry for the GSoC.
> I was wondering what is best way to fit security requirements of a mere
> application (login/password/roles).
This has been discussed in this list before. Check t
Hi,
I am creating a web application using Tapestry for the GSoC.
I was wondering what is best way to fit security requirements of a mere
application (login/password/roles).
How to keep and pass the user data from page to page ?
Should I use Tapestry mechanism to check access rights ? Like OnActi
16 matches
Mail list logo
