Re: [Acegisecurity-developer] setting attributes for remember-me cookie
Ben, I actually filed a JIRA issue on it yesterday, and submitted a patch: http://opensource.atlassian.com/projects/spring/browse/SEC-206 However, I had hoped to have some discussion on the list before submitting the patch because there was some questions about how defaults should be handled, and whether setting the path should be an property (or just implicitly set to root), or some mix of the two. The patch I submitted implicitly sets to root.. more details are in the jira issue and the patch itself. Hopefully it's useful. Feel free to discuss this further if you feel it needs to offer more flexibility. Thanks! -tim On 3/2/06, Ben Alex [EMAIL PROTECTED] wrote: Tim Kettering wrote: I scoured the forums and mailing list and did not find anyone bringing up this issue. I suspect it's because everyone (?) so far might have been using the filter based login. Which we are not, so this would not be a problem for them. Hi Tim If you are able to provide a JIRA patch that will provide this flexibility, I would be happy to apply it for you. Cheers Ben --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Home: http://acegisecurity.org Acegisecurity-developer mailing list Acegisecurity-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642 ___ Home: http://acegisecurity.org Acegisecurity-developer mailing list Acegisecurity-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
Re: [Acegisecurity-developer] setting attributes for remember-me cookie
Tim Kettering wrote: I scoured the forums and mailing list and did not find anyone bringing up this issue. I suspect it's because everyone (?) so far might have been using the filter based login. Which we are not, so this would not be a problem for them. Hi Tim If you are able to provide a JIRA patch that will provide this flexibility, I would be happy to apply it for you. Cheers Ben --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Home: http://acegisecurity.org Acegisecurity-developer mailing list Acegisecurity-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
[Acegisecurity-developer] setting attributes for remember-me cookie
Hi Everyone. Mabye there's already a really simple solution that's been staring me in the face but I'm not seeing it. I'm setting up the remember-me functionality for this project I'm working on, and due to project technical considerations, I've have to re-implement parts of the remember-me in the login controller instead of using the authentication filter. So basically what's happening is that on a successful login, the login controller will be making a call to the rememberMeServices.loginSuccess(), to set the remember-me cookie. But when I set out to test it, it didn't work. I dug around a bit and I think I found the problem, the application runs under the context /foo, and the login controller url is found at /foo/login, so the acegi remember-me cookie gets set with a path of /foo/login - which makes it fall out of scope when accessing /foo, if i understand the functionality of cookies right. So I've been looking at the code in acegi, and it seems like a Cookie is simply created with defaults in the TokenBasedRememberMeServices. So it would appear to me that I would need to subclass certain parts of this code to get it to set the path to something different than the default. I scoured the forums and mailing list and did not find anyone bringing up this issue. I suspect it's because everyone (?) so far might have been using the filter based login. Which we are not, so this would not be a problem for them. So, I thought I'd bring it up on the list.. see what you guys think should be done. -tim --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642 ___ Home: http://acegisecurity.org Acegisecurity-developer mailing list Acegisecurity-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
