We spent a week messing with this a few months ago.
I think the intention is that the Authentication object remain immutable.
Authentication is, as I remember, an interface and details on the
implemeting classes is sketchy at best. This leads me to believe that this
was meant to be part of the way
Honestly, I don't know. The method you tried originally is the one I
would've suggested. You might try searching Acegi's forums:
http://forum.springframework.org/forumdisplay.php?f=33
Matt
On 8/2/07, sionsmith <[EMAIL PROTECTED]> wrote:
>
> No i do not have that configure (well there are no entr
No i do not have that configure (well there are no entries in the
security.xml) I just want to be able to updates some properties in the
principle - is there anyway i can do this?
Many Thanks
Sion
mraible wrote:
>
> Do you have a userCache configured in security.xml? If so, you might
> try rem
Do you have a userCache configured in security.xml? If so, you might
try removing it.
Matt
On 7/31/07, sionsmith <[EMAIL PROTECTED]> wrote:
>
> Hi Appfuse Users,
>
> i'm using the acegi security framework to manage the user sessions within my
> project, the authentication & user details are retur
Hi Appfuse Users,
i'm using the acegi security framework to manage the user sessions within my
project, the authentication & user details are returned from a web service -
not the standard DAO's, however it acts the same.
The problem i have is the user in the SecurityContextHolder context is no
