tapestry-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kalle Korhonen <kalle.o.korho...@gmail.com>
Subject Re: Tynamo Security does not honor secure-enabled, @Security annotation?
Date Wed, 02 Nov 2011 03:33:53 GMT
On Tue, Nov 1, 2011 at 5:37 PM, Lenny Primak <lprimak@hope.nyc.ny.us> wrote:
> secure-enabled = true...
> I have a pretty simple authenticated page...
> @RequiresRoles(logical = Logical.OR, value = { Role.LogisticsRole, Role.AccountingRole,
Role.PalletsRole })
> @Secure
> public class TapPage
> {
> .......
> }
> When the page is redirected to the login screen (no authentication yet) and is called
from plain old http:// URL,
> the login screen is shown, but it's still the http:// protocol that is used.
> According to the Tapestry documentation @Scecure redirects to https:// URL if the page
is already not called through https.
> This works, until tynamo security gets involved and points to the login screen.
> Any chance of getting this fixed?

Please file an issue. I'll cut a new version of tapestry-security once
Shiro 1.2 and T5.3 is out.


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

View raw message