, 2006 4:27 PM
To: acegisecurity-developer@lists.sourceforge.net
Subject: Re: [Acegisecurity-developer] Preparing for 1.0.0 RC2
[EMAIL PROTECTED] wrote:
Paul,
I know it's been 3 weeks since you sent this and I'm
sorry not to
have replied. I have a number of professional and personal
-developer@lists.sourceforge.netSubject: RE:
[Acegisecurity-developer] Preparing for 1.0.0 RC2
Scott,
This is my
recommendation, the following snippets below shows how I cleanly got
Siteminder/Acegi to work.
Look at the requiresAuthentication() method below it
should
y other option off the top of my head would be to make sure the filter is
executed upon every request.
Scott
From: Garvey, Paul M (GE Commercial Finance)
[mailto:[EMAIL PROTECTED] Sent: Friday, February 10, 2006 11:28
AMTo:
acegisecurity-developer@lists.sourceforg
:
acegisecurity-developer@lists.sourceforge.netSubject: RE:
[Acegisecurity-developer] Preparing for 1.0.0 RC2
Scott,
You are partially right I
should not have to extend the SiteminderAuthenticationProcessingFilter to
makeAcegi work with Siteminder.
The
reason I was left
ilto:[EMAIL PROTECTED] On Behalf Of
Scott McCrorySent: Thursday, February 09, 2006 9:14
PMTo:
acegisecurity-developer@lists.sourceforge.netSubject: Re:
[Acegisecurity-developer] Preparing for 1.0.0 RC2
Paul,
I don'textend SiteminderAuthenticationProcessingFilter and override the
requiresAuthenticati
Paul,I don't extend SiteminderAuthenticationProcessingFilter and
override the requiresAuthentication() method because every one of my protected
action classes first checks to see if the user is authenticated (i.e. has an
security context holder) before processing the request. I do this by calling
