Re: tapestry-spring-security and openid

tication object if your regular authentication fails. Either omit it, or change the test to fail for the AnonymousAuthnticationToken. -Original Message- From: Ulrich Stärk [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 07, 2008 17:14 To: Tapestry users Subject: Re: tapestry-spring-secur

Re: tapestry-spring-security and openid

that should be omitted by default, but right now it will fill in > >> the > >> Authentication object if your regular authentication fails. Either omit > >> it, > >> or change the test to fail for the AnonymousAuthnticationToken. > >> &g

Re: tapestry-spring-security and openid

ion object if your regular authentication fails. Either omit >> it, >> or change the test to fail for the AnonymousAuthnticationToken. >> >> >> >> >>> -----Original Message----- >>> From: Ulrich Stärk [mailto:[EMAIL PROTECTED] >>> Se

Re: tapestry-spring-security and openid

Robin Helgelin schrieb: On Tue, Oct 7, 2008 at 10:58 PM, Jonathan Barker <[EMAIL PROTECTED]> wrote: I'm assuming this hasn't changed since tapestry5-acegi. The IfLoggedIn component uses the following test: private boolean test() { Principal principal = requestGlobals.getHTTPServle

Re: tapestry-spring-security and openid

PROTECTED] Sent: Tuesday, October 07, 2008 17:14 To: Tapestry users Subject: Re: tapestry-spring-security and openid Thanks Jonathan, but this not the root cause. The Authentication object stored in the SecurityContext is an AnonymousAuthenticationToken instead of an OpenIDAuthenticationToken. That tel

RE: tapestry-spring-security and openid

> Sent: Tuesday, October 07, 2008 17:29 > To: Tapestry users > Subject: Re: tapestry-spring-security and openid > > I already did this but this still doesn't solve the problem that there is > no openid Authentication > token in the SecurityContext. And I don't know wh

Re: tapestry-spring-security and openid

ationToken. -Original Message- From: Ulrich Stärk [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 07, 2008 17:14 To: Tapestry users Subject: Re: tapestry-spring-security and openid Thanks Jonathan, but this not the root cause. The Authentication object stored in the SecurityCon

RE: tapestry-spring-security and openid

To: Tapestry users > Subject: Re: tapestry-spring-security and openid > > On Tue, Oct 7, 2008 at 10:58 PM, Jonathan Barker > <[EMAIL PROTECTED]> wrote: > > I'm assuming this hasn't changed since tapestry5-acegi. The IfLoggedIn > > component uses

RE: tapestry-spring-security and openid

. Either omit it, or change the test to fail for the AnonymousAuthnticationToken. > -Original Message- > From: Ulrich Stärk [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 07, 2008 17:14 > To: Tapestry users > Subject: Re: tapestry-spring-security and openid > > Thanks J

Re: tapestry-spring-security and openid

On Tue, Oct 7, 2008 at 10:58 PM, Jonathan Barker <[EMAIL PROTECTED]> wrote: > I'm assuming this hasn't changed since tapestry5-acegi. The IfLoggedIn > component uses the following test: > >private boolean test() { >Principal principal = > requestGlobals.getHTTPServletRequest().getUserP

Re: tapestry-spring-security and openid

Thanks Jonathan, but this not the root cause. The Authentication object stored in the SecurityContext is an AnonymousAuthenticationToken instead of an OpenIDAuthenticationToken. That tells me that somehow the Authentication doesn't get stored... Uli Jonathan Barker schrieb: I'm assuming this

RE: tapestry-spring-security and openid

I'm assuming this hasn't changed since tapestry5-acegi. The IfLoggedIn component uses the following test: private boolean test() { Principal principal = requestGlobals.getHTTPServletRequest().getUserPrincipal(); return principal != null && principal.getName() != ""; } Unf