Well, hopefully we can move all of this stuff into a Tapestry Commons subproject of the TLP. Then we won't have these issues.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 30, 2006 11:17 AM To: users@tapestry.apache.org Subject: RE: Populating Tapestry ASO after successful Acegi Auth James: I can't get access to the svn repo. Can you send the jars? Thanks, -jason -----Original Message----- From: James Carman [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 30, 2006 10:41 AM To: 'Tapestry users' Subject: RE: Populating Tapestry ASO after successful Acegi Auth You can use the tapestry-acegi module found at [EMAIL PROTECTED] (if you can get the stupid anonymous login to work). If you can't let me know and I can send you the jar files directly. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 30, 2006 10:29 AM To: users@tapestry.apache.org Subject: RE: Populating Tapestry ASO after successful Acegi Auth Hi John, Just curious. . . would that code need to be inserted in *every* page's pageValidate() method considering that a user can bookmark or type in any secured URL? Acegi will intercept the request, throw up the Login page and then redirect to the requested page (which in this example would not be the default page and would therefore require it's on pageValidate() code) Or is there a more clever way to do this? Thanks, Tom -----Original Message----- From: Jonathan Barker [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 30, 2006 10:05 AM To: 'Tapestry users' Subject: RE: Populating Tapestry ASO after successful Acegi Auth I can't say it's a best practice, but it should be a reasonable strategy. In your pageValidate() method, if your ASO is not set Authentication auth = SecurityContext.getContext().getAuthentication(); If auth is not null Object principal = auth.getPrincipal(); If (principal instanceof UserDetails) Cast and put into ASO If you are using Hibernate or another persistence framework, and need to navigate the object graph from your ASO, reattach / refresh before doing it. I'm doing that in pageValidate() as well (and I'm using the Spring OSIV filter). It would be a little neater to extract out all of the Acegi stuff so your UI code doesn't depend on Acegi. Jonathan > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Wednesday, August 30, 2006 7:34 AM > To: users@tapestry.apache.org > Subject: Populating Tapestry ASO after successful Acegi Auth > > Greetings: > > I'm using Tapestry 4 and Acegi 1.0.1. I have acegi set up to perform > authentication using the AuthenticationProcessingFilter. I have a > requirement to place the domain object the Acegi UserDetails object is > based upon into a Tapestry ASO for use during the user session. =20 > > My question is: what the best practice for filling the Tapestry ASO with > the domain model's user object upon successful authentication with > Acegi? > > Thanks, > > -jason > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
