Acegi + Spring + Struts + Login

[Sonic]

Hy!

All is working fine, but at least one Problem.
I have a Login-Form with 3 fields sending to j_acegi_security_check.
j_username
j_password
test <-- has nothing to do with the login!!!

If username and password is OK my defaultTargetUrl is an Struts Action.
This is working fine too.

But where is test?
I need the third Parameter for the WebApp!
I´m new to Acegi + Spring + Struts.
Please an answer for beginners!

Thanks a lot
Sonic

[Sonic]

Hmmm!?!?!?

Please correct me if I´m wrong!
Acegi makes a redirect to the defaultTargetUrl or the Url I came from?!?
So I loose all my Parameters? (scope -> request)
Is there already a method to overrride or to implement so that I can 'rePopulate' the request? Can I define which Parameters are allowed to 'rePopulate' by a list of values? (If there is already a method)

If there is nothing, what can I do?

Thanks,
Sonic

[Ben Alex]

The SecurityEnforcementFilter has an AuthenticationEntryPoint which "launches" authentication. Usually you use the AuthenticationProcessingFilterEntryPoint for form-based login. SecurityEnforcementFilter also stores the HTTP GET request that caused the AuthenticationException, so that it can be redirected to late. JIRA has a task in it related to storing the HTTP POST parameters, but for now you'll need to ensure they're expressed as GET parameters. Most applications adopt a coarse-grained approach to filter security, such as /**=ROLE_USER (with specific ROLE_ANONYMOUS entries for login related concerns) and therefore you're not a fine-grained level of authorizing individual HTTP POST controllers. Use method authorization on the services layer for that instead.