For me
Authentication auth = new UsernamePasswordAuthenticationToken(
getUser(), getUser().getConfirmPassword(),
getUser().getAuthorities());
works fine.
mraible wrote:
>
> I would try it. If it works, please open an issue in JIRA and attach the
> patch.
>
> Matt
>
>
> On 9/7/07, carbon60 <[EMAIL PROTECTED]> wrote:
>>
>>
>> mraible wrote:
>> >
>> > I'm fine with normalizing it - patches welcome.
>> >
>>
>> Two things then:
>>
>> 1. Create a static method somewhere: getCurrentUser() that basically
>> contains the same code as posted previously;
>>
>> Does that sound about right? Where would you like the method?
>>
>> 2. Modify SignupController, around line 82, to put a real User object
>> into
>> the SecurityContext
>>
>> I'm not exactly sure how to go about this, since the current
>> UsernamePasswordAuthenticationToken is supposed to be for simple strings.
>> Although the existing UserSecurityAdvice class does seem to stuff a User
>> object in there.
>>
>> Comments?
>>
>> A.
>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/after-user-signup-there-is-username-placed-as-principal%2C-why-not-user-pojo--tf4366000s2369.html#a12562312
>> Sent from the AppFuse - User mailing list archive at Nabble.com.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
> --
> http://raibledesigns.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/after-user-signup-there-is-username-placed-as-principal%2C-why-not-user-pojo--tf4366000s2369.html#a12592042
Sent from the AppFuse - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
