Sergio Bossa wrote:
I don't see how implementing a custom AuthenticationEntryPoint would
solve my problem, which is not related to the login page, but rather
to the page displayed after successfull login.
It could be done by using the AuthenticationEntryPoint to modify the
target URL defined by
AbstractProcessingFilter.ACEGI_SECURITY_TARGET_URL_KEY. That way,
irrespective of which authentication entry point you might ultimately
switch to (CAS, form etc), your AuthenticationEntryPoint will be
compatible with all of them. You could even store the original target
URL in a different session attribute, and thus after your post-login
page is displayed, you could still offer a pass-through to the
originally requested page.
Best regards
Ben
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Home: http://acegisecurity.org
Acegisecurity-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
