[Flow] InitializeAction called before reauthentication

[Christian Loock]

Well the Problem here is, that it is actually stored in the security 
context, which i cannot really alter.


On 03.04.2014 09:47, Aimo Kuenkel wrote:
> Hi Christian,
>
> maybe have a look at this issue http://forge.typo3.org/issues/57374, we had the same problem here and solved that by just storing the identifier of the object we tried to save in the session.
> I'd say that behaviour is a bug, so i created that issue.
>
> Is that the problem you are experiencing?
>
> Greetings,
>
> Aimo
>
> -----Ursprüngliche Nachricht-----
> Von: flow-bounces at lists.typo3.org [mailto:flow-bounces at lists.typo3.org] Im Auftrag von Christian Loock
> Gesendet: Donnerstag, 3. April 2014 09:35
> An: TYPO3 Flow mailing list
> Betreff: Re: [Flow] InitializeAction called before reauthentication
>
> I'm working on Version 2.1.
>
> AS far as i can tell, the problem seems to be in a different location then I originally thought. The security context in the initializeAction seems to be working, but my Party Object which is restored from the session, does not seem to get to work correctly. I'm trying to get assigned accounts in the initializeObject method of my Party Object (which extends TYPO3\Party\Domain\Model\Person). However, the accounts property of the Party object is Null when i try to access it in the initializeObject method. It seems to be filled somewhere after initializeObject is called, since i can access it at a later point :(
>
>
> On 03.04.2014 09:27, Aimo Kuenkel wrote:
>> Hi there,
>>
>> We have a controller with an initializeAction that calls a userService that asks the securityContext with getAccount() and then returns $account->getParty() - and that's definitely working.
>> So i get and work with the logged in user inside the initializeAction.
>> We're on 2.2beta1, what version are you talking about?
>>
>> Greetings,
>>
>> Aimo
>>
>> -----Ursprüngliche Nachricht-----
>> Von: flow-bounces at lists.typo3.org
>> [mailto:flow-bounces at lists.typo3.org] Im Auftrag von Adrian Föder
>> Gesendet: Donnerstag, 3. April 2014 09:10
>> An: flow at lists.typo3.org
>> Betreff: Re: [Flow] InitializeAction called before reauthentication
>>
>> Hi Christian,
>>
>> well, that's simply correct.
>> The initialize actions are rather meant for property mapping corrections etc., if you need more sophisticated handling, put it in the actual controller action method itself or in a service.
>>
>> Best,
>> Adrian
>>
>> Am 02.04.2014 15:15, schrieb Christian Loock:
>>> Hi,
>>>
>>> i wonder if it is on purpose, that my controller's initalizeAction
>>> method gets called, before the security context is initialized. This
>>> way, i cant do anything that is Userrelated in this methods, which
>>> does not seem right to me. Can anybody enlighten me about this?
>>>
>>> --
>>> Cheers,
>>>
>>> Christian
>>>
>> _______________________________________________
>> Flow mailing list
>> Flow at lists.typo3.org
>> http://lists.typo3.org/cgi-bin/mailman/listinfo/flow
>> _______________________________________________
>> Flow mailing list
>> Flow at lists.typo3.org
>> http://lists.typo3.org/cgi-bin/mailman/listinfo/flow
> --
> Cheers,
>
> Christian
>
> _______________________________________________
> Flow mailing list
> Flow at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/flow
> _______________________________________________
> Flow mailing list
> Flow at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/flow

-- 
Cheers,

Christian